fix: move @eslint/js release after other packages (#203)

eslint · Mar 29, 2024 · f8f72ef · f8f72ef
1 parent 98e99cb
commit f8f72ef
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/src/plugins/recurring-issues/index.js b/src/plugins/recurring-issues/index.js
@@ -21,8 +21,8 @@ The next scheduled release will occur on ${releaseDate.format("dddd, MMMM Do, YY
 
 - [ ] Remove the 'tsc agenda' label on this issue
 - [ ] Review open pull requests and merge any that are [ready](https://eslint.org/docs/maintainer-guide/pullrequests#when-to-merge-a-pull-request)
-- [ ] Release \`@eslint/js\` to match the upcoming \`eslint\` version in [Jenkins](https://jenkins2.eslint.org)
 - [ ] 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](https://jenkins2.eslint.org)
 - [ ] 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](https://jenkins2.eslint.org)
 - [ ] Update the release blog post: