The next scheduled release will occur on Friday, June 27th, 2025.

Release Day Checklist

• Remove the 'tsc agenda' label on this issue
• Review open pull requests and merge any that are ready
• Verify if there are other packages (i.e., espree, eslint-scope, eslint-visitor-keys, @eslint/eslintrc) that need to be released first
• Release @eslint/js to match the upcoming eslint version in Jenkins
• Update package.json in the eslint repo with new versions from the preceding steps (create and merge a pull request)
• Start the release on Jenkins
• Update the release blog post:
  • Add a "Highlights" section for any noteworthy changes.
  • In the authors frontmatter, replace eslintbot with your GitHub username.
  • Remove the draft: true line in frontmatter.
• Make a release announcement on Twitter
• Make a release announcement in the Discord '#announcements' channel
• Add a comment to this issue saying the release is out
• Add the 'patch release pending' label to this issue

Two Days After Release Day Checklist

Typically Monday for regular releases; two days after patch releases.

• Check the issues list for any regression issues

No Regressions Checklist

• Remove the 'patch release pending' label from this issue
• Close this issue

Patch Release Checklist

• Resolve the regression by merging any necessary fixes
• Start the release on Jenkins
• Update the release blog post:
  • Add a "Highlights" section for any noteworthy changes.
  • In the authors frontmatter, replace eslintbot with your GitHub username.
  • Remove the draft: true line in frontmatter.
• Make a release announcement on Twitter
• Make a release announcement in the Discord '#announcements' channel
• Add a comment to this issue saying the release is out
• Wait two days and repeat the Two Days After a Release checklist
• Close this issue

Followup

Please use this issue to document how the release went, any problems during the release, and anything the team might want to know about the release process. This issue should be closed after all patch releases have been completed (or there was no patch release needed).

Resources:

• Release guidelines