fix(expo-cicd-workflows): pin dependency versions to exact semver in package.json#53
Open
xiaolai wants to merge 1 commit into
Open
fix(expo-cicd-workflows): pin dependency versions to exact semver in package.json#53xiaolai wants to merge 1 commit into
xiaolai wants to merge 1 commit into
Conversation
…package.json Co-Authored-By: Claude Code <noreply@anthropic.com>
This was referenced Apr 27, 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
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.
Security Fix (Low — Supply Chain Hygiene)
plugins/expo/skills/expo-cicd-workflows/scripts/package.jsonspecifies all three dependencies with caret (^) semver ranges:Caret ranges allow automatic minor and patch upgrades. Without a committed lockfile, any fresh
npm installcan pull in a newer version — including one that has been supply-chain-compromised. Pinning to exact versions makes the resolved version explicit and auditable regardless of whether a lockfile is present.Fix: Remove the
^prefix from all three dependencies, pinning them to the versions already in use.Intentional upgrades can still be performed via
npm install ajv@latestfollowed by a review and re-pin — this PR simply makes the current resolved version the default.