Skip to main content

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/
  3. If necessary, test main locally in the:
    1. stylelint/stylelint-config-recommended
    2. stylelint/stylelint-config-standard
    3. stylelint/
  4. 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
    7. Confirm the creation of the release at
  5. If necessary, release stylelint-config-*:
    1. Change to the stylelint-config-* repository.
    2. Repeat steps 5 to 8 above for that repository.
  6. Update the website:
    1. Change to the repository.
    2. Run npm install${new_version} --save-dev (replacing ${new_version} with the version number e.g. 14.13.2).
    3. Run npm test.
    4. Commit these changes.
    5. Push these changes.
    6. Confirm the deployment of the update to
  7. Check that installs the latest Stylelint and config versions.
  8. Compose a tweet that:
    • announces the release
    • communicates what has changed
    • links to the appropriate heading in the changelog on

New release issue template‚Äč

- [ ] stylelint release
- [ ] stylelint-config-recommended update/release
- [ ] stylelint-config-standard update/release
- [ ] update
- [ ] stylelint-demo check
- [ ] tweet