Repository navigation
Bump eslint to 10.13.0 and typescript-eslint to 8.72.0 - #5
Merged
Merged
Conversation
Both are patch-level bumps of existing devDependencies; the lockfile is regenerated with npm from the registry. The lint run reports no new findings.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps eslint from ^10.12.0 to ^10.13.0 and typescript-eslint from ^8.71.1 to ^8.72.0 (same range style as before) and regenerates package-lock.json with npm from the registry.
Takes pulp#389.
The new versions report nothing new: npm run eslint, lint:ts, lint:sass and prettier:check give the same result as before (warnings only, from the existing restricted-import rule), and npm test passes. No source changes were needed.