Scheduled release for December 29th, 2023

[eslint-github-bot]

The next scheduled release will occur on Friday, December 29th, 2023.

Release Day Checklist

• Remove the 'tsc agenda' label on this issue
• Review open pull requests and merge any that are ready
• Release @eslint/js to match the upcoming eslint version in Jenkins
• Verify if there are other packages (i.e., espree, eslint-scope, eslint-visitor-keys, @eslint/eslintrc) that need to be released first
• 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 (not required for prereleases)

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

[mdjermanovic]

ESLint v9.0.0-alpha.0 has been released:

https://eslint.org/blog/2023/12/eslint-v9.0.0-alpha.0-released/

Since this is a prerelease, feel free to continue merging PRs, but we'll keep this issue open in case we need to do an immediate follow-up release on Monday.

[mdjermanovic]

The release process went pretty well considering the amount of changes we've had since the last major release.

But, there were two problems we should fix:

1. The release process didn't update any files under docs/, so we had to run npm build:site locally and push the changes (docs: update docs for v9.0.0-alpha.0 #17929).
2. While doing that, I noticed that the script added the two recently removed rules (require-jsdoc and valid-jsdoc) to the rule_versions.json file as if they were added in v9.0.0-alpha.0. I removed those entries, but it's likely that the same will happen again during the next release. edit: my mistake, those entries are actually correctly added to removed.

[mdjermanovic]

There were no issues that would require a follow-up release, so this concludes the v9.0.0-alpha.0 release.

The problem with updating files in the docs directory should be fixed by #17940.