New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scheduled release for April 19th, 2024 #18293
Comments
Release plan:
|
After releasing To fix the build, we had to revert part of the changes of 4d11e56, (in 50d406d) and release a patch of @eslint/js v9.1.1. |
ESLint v9.1.0 has been released: https://eslint.org/blog/2024/04/eslint-v9.1.0-released/ Please merge semver-patch PRs only until we determine whether or not a patch release is necessary. |
I'm trying to understand if #18374 is caused by a regression. According to the issue, ESLint does not stop its execution automatically, which should not happen in case of a misconfiguration. |
ESLint v9.1.1 has been released: |
This concludes the v9.1.0 and v9.1.1 releases. We can resume merging semver-minor changes. |
The next scheduled release will occur on Friday, April 19th, 2024.
Release Day Checklist
espree
,eslint-scope
,eslint-visitor-keys
,@eslint/eslintrc
) that need to be released first@eslint/js
to match the upcomingeslint
version in Jenkinspackage.json
in theeslint
repo with new versions from the preceding steps (create and merge a pull request)authors
frontmatter, replaceeslintbot
with your GitHub username.draft: true
line in frontmatter.Two Days After Release Day Checklist
Typically Monday for regular releases; two days after patch releases.
No Regressions Checklist
Patch Release Checklist
authors
frontmatter, replaceeslintbot
with your GitHub username.draft: true
line in frontmatter.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:
The text was updated successfully, but these errors were encountered: