[INFRA] Allow only update of dependencies to patch versions #1990
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.
In the past, a local 'npm install' run bumped some eslint extensions to minor releases. They included new rules that
broke the lint checks. It was hard to understand why the errors popped suddenly and disturbed developments.
This should not happen with patch updates.
Notes
I started implementing this in dependabot Pull Requests, for instance in #1985.
This PR set the rule to all devDependencies and dependencies that were previously allowed minor updates (
^x.y.z
).See https://nodejs.dev/learn/semantic-versioning-using-npm