ci: use stable ESLint v10 in the CI #374
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the CI test matrix to validate this repo against the stable ESLint v10 line (rather than a v10 release-candidate range), aligning CI coverage with the newly published stable major.
Changes:
- Replaced the ESLint matrix entry
^10.0.0-rc.0with10.xin the CI workflow.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
nzakas
approved these changes
Feb 9, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prerequisites checklist
What is the purpose of this pull request?
This PR updates the CI workflow to use the stable release of ESLint v10, published about 12 hours ago.
In #365, the CI workflow used a pre-release version to ensure this plugin works well with ESLint v10, but now that the stable release has been published, there is no need to use the pre-release for CI checks.
What changes did you make? (Give an overview)
This PR updates the CI workflow to use the stable release of ESLint v10, published about 12 hours ago.
Related Issues
N/A
Is there anything you'd like reviewers to focus on?
N/A