feat(renovate): pin npm deps to exact versions org-wide - #5
Merged
Conversation
Add :pinAllExceptPeerDependencies so dependencies/devDependencies pin to exact versions (peerDependencies stay ranges). config:recommended preserved whatever range style each manifest used, so deps like @astrojs/starlight stayed on carets (^0.39.0) and silently drifted within-range between installs. The org has no published npm library (shared-ui is private, consumed from GitHub at build time), so no downstream consumer depends on these ranges — exact pins give reproducible installs and clean update diffs. Enabling this opens a one-time 'Pin dependencies' PR per repo (update type 'pin', which the automerge rule does not match, so each is human-reviewed).
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.
Why
config:recommendedpreserves whatever range style each manifest already uses, so the org has never enforced a version strategy for npm deps. That's why@astrojs/starlightstayed^0.39.0(caret) — Renovate just bumps the range, never pins. Within-range drift between installs is invisible in PRs.Change
Add
:pinAllExceptPeerDependenciesto the presetextends:dependencies+devDependencies→ pinned exact (^0.39.0→0.39.0)peerDependencies→ stay as ranges (correct for any consumer)The org has no published npm library (
shared-uiisprivate, fetched from GitHub at build time), so no downstream consumer relies on these ranges — pinning is safe org-wide and gives reproducible installs + reviewable diffs.Rollout
On Renovate's next scan, each repo gets one 'Pin dependencies' PR converting all carets to exact. That PR's update type is
pin, which the automerge rule (patch/digest) does not match — so each is reviewed by a human, then ongoing patch bumps automerge as before.Validated locally with
renovate-config-validator --strict.