- Create a new issue to announce the planned release:
- include the template checklist
- If necessary, test
main
locally in the: - Release Stylelint:
- If necessary, reorder the changelog entries in the "Prepare release" pull request so that the widest-reaching changes come first
- Merge the "Prepare release" pull request.
- Open a terminal window in the
stylelint
repository. - Run
npm run release
. - Select the version from the
np
prompt that matches the one in the changelog. - Confirm the publishing of the package to www.npmjs.com/package/stylelint.
- Confirm the creation of the release at github.com/stylelint/stylelint/releases.
- If necessary, release
stylelint-config-*
:- Change to the
stylelint-config-*
repository. - Repeat steps 5 to 8 above for that repository.
- Change to the
- Update the online demo:
- Change to the
stylelint-demo
repository - Run
npm install stylelint@latest --save
. - Run
npm test
. - Commit these changes.
- Push these changes.
- If necessary, install the Heroku CLI
- If necessary, login using the Stylelint Heroku account:
heroku login
- If necessary, set up a remote:
heroku git:remote -a stylelint-demo
- Push the code:
git push heroku main
- Confirm the deployment of the update to stylelint.io/demo.
- Change to the
- Update the website:
- Change to the
stylelint.io
repository - Run
npm install https://github.com/stylelint/stylelint/tarball/${new_version} --save-dev
(replacing${new_version}
with the version number e.g.14.13.2
). - Run
npm test
. - Commit these changes.
- Push these changes.
- Confirm the deployment of the update to stylelint.io.
- Change to the
- Compose a tweet that:
- announces the release
- communicates what has changed
- links to the appropriate heading in the changelog on stylelint.io.
- [ ] stylelint release
- [ ] stylelint-config-recommended update/release
- [ ] stylelint-config-standard update/release
- [ ] stylelint-demo update
- [ ] stylelint.io update
- [ ] tweet