Performing releases

1. Create a new issue to announce the planned release:
   • include the template checklist
   • if applicable, list any new rules so that we can discuss including them in our configs
2. If necessary, open a pull request to mark those rules in docs/user-guide/rules.md.
3. Check if package tests in stylelint/stylelint-ecosystem-tester fail with the new version.
4. If necessary, test the main branch locally against:
   1. stylelint/stylelint-config-recommended
   2. stylelint/stylelint-config-standard
   3. stylelint/stylelint.io
5. Release Stylelint:
   1. If necessary, reorder the changelog entries in the "Prepare x.y.z" pull request so that the widest-reaching changes come first.
   2. Merge the "Prepare x.y.z" pull request.
   3. Open a terminal window in the stylelint repository.
   4. Run npm run release.
   5. Select the version from the np prompt that matches the one in the changelog.
   6. Confirm the publishing of the package to www.npmjs.com/package/stylelint.
   7. Confirm the creation of the release at stylelint/stylelint/releases.
6. If necessary, release stylelint-config-*:
   1. Change to the stylelint-config-* repository.
   2. Repeat steps 5 to 8 above for that repository.
7. Update the website:
   1. Go to the releasing action page in the stylelint.io repository.
   2. Click Run workflow.
   3. Check and merge a pull request created by the action.
   4. Confirm the deployment of the update to stylelint.io.
8. Check that stylelint.io/demo installs the latest Stylelint and config versions.
9. 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-ecosystem-tester check
- [ ] stylelint release
- [ ] stylelint-config-recommended update/release
- [ ] stylelint-config-standard update/release
- [ ] stylelint.io update
- [ ] stylelint-demo check
- [ ] tweet