fix: pin exact dependency versions in apps/task-manager/package.json#44
Open
xiaolai wants to merge 1 commit into
Open
fix: pin exact dependency versions in apps/task-manager/package.json#44xiaolai wants to merge 1 commit into
xiaolai wants to merge 1 commit into
Conversation
Caret ranges allow unreviewed minor and patch updates to install automatically. Pinning to exact versions ensures reproducible installs and surfaces upgrades as explicit review decisions. Co-Authored-By: Claude Code <noreply@anthropic.com>
This was referenced Apr 26, 2026
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's changed
apps/task-manager/package.jsonuses caret (^) semver ranges for all four dependencies:With
^, npm and Bun will silently install any compatible minor/patch release on a freshinstall. This means the installed version can differ between environments and CI runs, and a supply-chain compromise of any of these packages at a minor/patch version would be picked up automatically.Fix
Pinned all four ranges to exact versions. The currently resolved versions (
5.3.0,17.7.2,1.1.6,17.0.32) are preserved — this is a no-op for anyone who already has a lockfile; it only affects fresh installs without one.Upgrades should now be explicit commits rather than silent side-effects of
npm install.