Pin production dependencies to exact versions - #250
Merged
Merged
Conversation
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
No issues found across 3 files
Auto-approved: Pins production dependencies to exact currently locked versions in package.json and package-lock.json, and removes the Renovate rangeStrategy bump setting so future updates are properly age-gated. Behavior-preserving at current versions; no version changes or new exposure.
Re-trigger cubic
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.
Summary
Pin all
dependenciesinpackage.jsonto exact versions (matching the currently locked/resolved versions onmain) and remove the global"rangeStrategy": "bump"from.github/renovate.json.Why: with caret ranges +
rangeStrategy: bump, every in-range update was classified asupdateType: bump, which Renovate explicitly excludes fromminimumReleaseAgeenforcement (same forlockfileUpdate/rollbackviasecurity:minimumReleaseAgeNpm), producing the "manually validate the Minimum Release Age" warning seen on e.g. #247. With exact pins, future updates arepatch/minor/major, which are age-gated, and every update touchespackage.json, so the stale-lock revert loop from #246 cannot recur.Note:
@scalar/hono-api-referenceis pinned to0.12.4(the locked version) rather than the^0.12.2floor, to avoid a downgrade.