Performing releases
- Create a new issue announcing the planned release, e.g.
Release 8.11.1 and include the template checklist.
- Locally test
master in the stylelint-config-* shareable config repositories. Install current master branch (npm install stylelint/stylelint#master) and run tests.
- Locally test
master in the stylelint/stylelint.io repository.
- Locally test
master in the stylelint/stylelint-demo repository.
- Publish the package to npm and create a GitHub release using
np:
- Consistently format the changelog.
- Replace
## Head with new version number e.g. ## 8.1.2.
- Commit these changes.
- Push these changes.
- Confirm the changes are correct at https://github.com/stylelint/stylelint.
- Run
npm run release.
- Select the version that matches the one from the changelog.
- Copy and paste the changelog entries for the published version from changelog when the GitHub release page opens.
- Confirm the publishing of the package to https://www.npmjs.com/package/stylelint.
- Confirm the creation of the release at https://github.com/stylelint/stylelint/releases.
- If a new version of any
stylelint-config-* is required, repeat step 5 for that repository.
- Update the online demo by changing to the
stylelint-demo repository:
- Run
npm install -S stylelint@latest.
- Run
npm test.
- Commit these changes.
- Push these changes.
- Confirm the deployment of the update to stylelint.io/demo.
- Update the website documentation by changing to the
stylelint.io repository:
- Run
npm install -D stylelint@latest.
- Run
npm test.
- Commit these changes.
- Push these changes.
- Confirm the deployment of the update to stylelint.io.
- Compose a tweet that:
- announces the release
- communicates what has changed
- links to the appropriate heading in the changelog on stylelint.io.
New release issue template
- [ ] stylelint release
- [ ] stylelint-config-recommended update/release
- [ ] stylelint-config-standard update/release
- [ ] stylelint-demo update
- [ ] stylelint.io update
- [ ] tweet
cc @stylelint/core