Repository navigation
fix: nudge for a missing lockfile instead of blocking - #84
Merged
Merged
Conversation
algomaster99
force-pushed
the
feat/new-manifest-lockfile-nudge
branch
from
October 2, 2026 15:43
7197f19 to
ec41049
Compare
algomaster99
changed the title
A range that allows latest no longer blocks on a missing lockfile; it passes with a nudge to generate one. A range that excludes latest gets only the suggestion to update the range, now worded "update range to" instead of "widen to". Exact pins are unaffected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
algomaster99
force-pushed
the
feat/new-manifest-lockfile-nudge
branch
from
October 2, 2026 15:47
ec41049 to
eb25615
Compare
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
algomaster99
commented
Oct 2, 2026
Co-Authored-By: Claude Opus 5.5 <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.
yul blocked any range with no lockfile next to its manifest, even one that already allows latest. A new manifest can't have a lockfile yet, so an agent without the toolchain got stuck: in the Opus benchmark, 10 Cargo and 7 PyPI hook runs never wrote their manifest. Now a missing lockfile never blocks on its own.
-> <latest>-> <latest>widen to ^<latest>(+ no-lockfile line)update range to ^<latest>The nudge goes to Claude as
additionalContext:🤖 Generated with Claude Code