Skip to content

Commit

Permalink
fix(nightly-ci): apply some fixes for nightly releases
Browse files Browse the repository at this point in the history
  • Loading branch information
ineshbose committed Dec 16, 2023
1 parent 108b183 commit 6cc7ae3
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 11 deletions.
9 changes: 5 additions & 4 deletions .github/workflows/nightly.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,9 @@ name: nightly release

on:
workflow_run:
workflows:
- ci
workflows: [ci]
types: [completed]
branches: [main]

jobs:
nightly:
Expand All @@ -21,7 +22,7 @@ jobs:
- run: pnpm install
- run: pnpm build

- run: pnpm changelogen --bump --canary --publish
- run: pnpm changelogen --bump --canary --publish --publishTag nightly
env:
NODE_AUTH_TOKEN: ${{ secrets.NODE_AUTH_TOKEN }}
NODE_AUTH_TOKEN: ${{ secrets.NPM_AUTH_TOKEN }}
NPM_CONFIG_PROVENANCE: true
13 changes: 6 additions & 7 deletions docs/content/1.getting-started/1.setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,18 +58,17 @@ After each commit is merged into the `main` branch of `@nuxtjs/tailwindcss` and

You can opt in to use this release channel and avoid waiting for the next release and helping the module by beta testing changes.

The build and publishing method and quality of nightly releases are the same as stable ones. The only difference is that you should often check the [GitHub repository](https://github.com/nuxt/image) for updates. There is a slight chance of regressions not being caught during the review process and by the automated tests. Therefore, we internally use this channel to double-check everything before each release.
The build and publishing method and quality of nightly releases are the same as stable ones. The only difference is that you should often check the [GitHub repository](https://github.com/nuxt-modules/tailwindcss) for updates. There is a slight chance of regressions not being caught during the review process and by the automated tests. Therefore, we internally use this channel to double-check everything before each release.

<!-- TODO -->
<!-- #### Opting into the nightly channel
### Opting into the nightly channel

Update `@nuxtjs/tailwindcss` dependency inside `package.json`:

```diff [package.json]
{
"devDependencies": {
- "@nuxtjs/tailwindcss": "^6.10.0"
+ "@nuxtjs/tailwindcss": "npm:@nuxtjs/tailwindcss-edge@latest"
+ "@nuxtjs/tailwindcss": "npm:@nuxtjs/tailwindcss@nightly"
}
}
```
Expand All @@ -83,13 +82,13 @@ Update `@nuxtjs/tailwindcss` dependency inside `package.json`:
```diff [package.json]
{
"devDependencies": {
- "@nuxtjs/tailwindcss": "npm:@nuxtjs/tailwindcss@latest"
+ "@nuxtjs/tailwindcss": "^1.0.0"
- "@nuxtjs/tailwindcss": "npm:@nuxtjs/tailwindcss@nightly"
+ "@nuxtjs/tailwindcss": "^6.10.0"
}
}
```

Remove lockfile (`package-lock.json`, `yarn.lock`, or `pnpm-lock.yaml`) and reinstall dependencies. -->
Remove lockfile (`package-lock.json`, `yarn.lock`, or `pnpm-lock.yaml`) and reinstall dependencies.

## Tailwind Files

Expand Down

0 comments on commit 6cc7ae3

Please sign in to comment.