chore(deps): upgrade lint-staged to 17#53
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Upgrade lint-staged from 16.4.0 to 17.0.8 and carry its normal lockfile resolution on top of the repaired frontend baseline and TypeScript 7.
Why
The standalone Dependabot PR #42 was built on the earlier malformed lockfile stack. This replacement keeps the update isolated while preserving all dependency work already merged through #51 and #52.
Testing
Risks
Low to moderate tooling-major risk. lint-staged 17 requires Node 22.22.1 or newer, which matches the repository CI/toolchain baseline.
Lockfile rationale
package-lock.json applies the normal lint-staged 17 resolution to the current TypeScript 7 lockfile without changing unrelated application dependencies.
Screenshots
Not applicable; no UI changes.