ci: use --force
flag when installing eslint
#17921
Merged
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.
Temporary solution for prerelease versions
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain:
Prerelease versions of
eslint
will likely need to be installed usingnpm install --force
, because some of the dependencies and dev dependencies haveeslint
as a peer dependency, and prereleases most likely won't satisfy those range constraints.I prepared this so that we can quickly fix the CI after today's v9.0.0-alpha.0 release. Do not merge yet.
What changes did you make? (Give an overview)
Updated ci workflows to use the
--force
flag when installing eslint.Is there anything you'd like reviewers to focus on?
Did I miss some places?