Repository navigation
fix: preserve locked uv package identities in dependency scopes - #2515
Draft
groupthinking wants to merge 1 commit into
Draft
groupthinking wants to merge 1 commit into
groupthinking wants to merge 1 commit into
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This branch was successfully deployed
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.
Canonical issue
Closes #2514
Follow-up to the post-merge review on #2492. The original repair is merged and GRV-861 remains completed.
Outcome
A lock containing runtime
split@1.0and development-onlysplit@2.0 -> dev-child@1.0now keeps the latter two packages development-scoped. Previously, name-only traversal promoted all three to runtime and the recorder accepted those incorrect rows.Scope
Only the classifier, recorder, and their tests change. This is a classification correction, not a new vulnerability or production-exposure finding.
Risk
Low: CI dependency-graph tooling only. Ambiguous/unresolved references now fail closed rather than assigning guessed scopes. The existing root-selection and dev/docs policy remain as before. The recorder's API projection cannot independently distinguish a source-only change with identical package name/version. Hosted behavior for the new tree is not yet verified.
Rollback: revert this commit; doing so restores the reproduced classification defect.
Verification
Patch commit:
c68b06b37253ffce04840e8f137eae625046cc81Base:
f258db8a6cc38c064ba4d7ca1baee02bedbd0534Tested tree (identical to remote commit tree):
195f14846513dffb4943f862a59fbe42b0d9d12cLocal environment: Python 3.12.14, pytest 9.2.0, pytest-asyncio 1.4.1, PyYAML 6.0.3, Ruff 0.17.3 in an isolated venv.
Before the correction, the first regression set produced 14 failed / 8 passed against the old implementation. That run explicitly reproduced both incorrectly runtime-classified packages and the recorder accepting both incorrect API rows. Four additional source-precedence cases were added before the final 55-test passing run.
Production evidence
Not applicable to this local classification correction. No production-deployment or hosted snapshot-verification claim is made. Tests use synthetic lockfiles and injected API responses; they do not submit dependency snapshots.
Agent handoff
Keep this PR in draft for review. Do not merge automatically.