pin-override: re-resolve in range before writing any resolution - #30
Merged
Conversation
Most of what Dependabot leaves open never needed a resolution. It needed the lockfile re-resolved inside the ranges the tree already declares, which is `yarn up -R <pkg>` with no version: every copy moves to the newest its own parent allows, package.json untouched. Dependabot cannot do that — it targets one exact version for a name across the tree and gives up when any copy cannot reach it, so brace-expansion at 1.x, 2.x and 5.x under three minimatch parents was "unfixable" to it while each copy sat one patch from clear. It also cannot touch a fix a hand-closed PR taught it to ignore; this pass never asks it. Measured across the fleet on 2026-09-11 in scratch worktrees: 220 audit findings to 102, no manifest changed anywhere. fundraiser-api's axios, 29 advisories held for a month behind a closed PR, moved 1.9.0 -> 1.20.0 inside its own ^1.3.6. The pass keeps only what cleared an advisory (two runs: discover, then keep), abandons itself if package.json ever changes, and the resolution pass runs on whatever survives with a re-read tree. New `bumped` output for the PR body; `changed` is true when either pass did something. Dry run skips the pass, as it cannot preview it without writing the lockfile. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Most of what Dependabot leaves open never needed a resolution. It needed the
lockfile re-resolved inside the ranges the tree already declares, which is
yarn up -R <pkg>with no version: every copy moves to the newest its ownparent allows, package.json untouched. Dependabot cannot do that — it targets
one exact version for a name across the tree and gives up when any copy cannot
reach it, so brace-expansion at 1.x, 2.x and 5.x under three minimatch parents
was "unfixable" to it while each copy sat one patch from clear. It also cannot
touch a fix a hand-closed PR taught it to ignore; this pass never asks it.
Measured across the fleet on 2026-09-11 in scratch worktrees: 220 audit
findings to 102, no manifest changed anywhere. fundraiser-api's axios, 29
advisories held for a month behind a closed PR, moved 1.9.0 -> 1.20.0 inside
its own ^1.3.6.
The pass keeps only what cleared an advisory (two runs: discover, then keep),
abandons itself if package.json ever changes, and the resolution pass runs on
whatever survives with a re-read tree. New
bumpedoutput for the PR body;changedis true when either pass did something. Dry run skips the pass, as itcannot preview it without writing the lockfile.
Release
Minor: cut
v14.6.0and movev14. Consumers pick it up with no PR. The template independency-policyis updated alongside to render the newbumpedoutput.🤖 Generated with Claude Code