Skip to main content

Performing releases

  1. Create a new issue to announce the planned release:
  2. If necessary, test main locally in the:
    1. stylelint/stylelint-config-recommended
    2. stylelint/stylelint-config-standard
    3. stylelint/stylelint-demo
    4. stylelint/
  3. Release Stylelint:
    1. If necessary, reorder the changelog entries in the "Prepare release" pull request so that the widest-reaching changes come first
    2. Merge the "Prepare release" 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
  4. If necessary, release stylelint-config-*:
    1. Change to the stylelint-config-* repository.
    2. Repeat steps 5 to 8 above for that repository.
  5. Update the online demo:
    1. Change to the stylelint-demo repository
    2. Run npm install stylelint@latest --save.
    3. Run npm test.
    4. Commit these changes.
    5. Push these changes.
    6. If necessary, install the Heroku CLI
    7. If necessary, login using the Stylelint Heroku account: heroku login
    8. If necessary, set up a remote: heroku git:remote -a stylelint-demo
    9. Push the code: git push heroku main
    10. Confirm the deployment of the update to
  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. 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
- [ ] stylelint-demo update
- [ ] update
- [ ] tweet