Repository navigation
test: check v0.2.0 snapshot manifest mapping on fast-uri update - #2494
Closed
groupthinking wants to merge 6 commits into
Closed
groupthinking wants to merge 6 commits into
groupthinking wants to merge 6 commits into
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
🔍 PR Validation |
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 |
Contributor
✅ E2E Test Results: ALL TESTS PASSED
Test Output |
Contributor
Dependency ReviewThe following issues were found:
|
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.
Result — failed diagnostic, closed unmerged
The v0.2.0 action did not restore a trustworthy dependency comparison in hosted run 40669620295 at base
ba2777d1b008c2148d413e07cc497791966310e0and head95303d82bf8f09f9f6dd89a58119d6b716bd7ada.../../_temp/dependency-review-base/. The expectedpackage-lock.jsonfast-uri 3.1.7 → 3.1.9 change is present, but this diff cannot support a clean dependency verdict.This canary is closed without merging. Issue #2490 and draft fix PR #2492 remain open. The earlier full-tree parity proposal and the v0.2.0 action update have not been proven to fix the current base snapshot state. The original diagnostic criteria below remain unmet.
Diagnostic purpose
Refs #2490, #2492 and the original action update #2397. This is a temporary draft canary; do not merge it. The prior canary #2493 scanned the full tree with component-detection action v0.1.6, yet GitHub reported three base snapshots versus one head snapshot and 55 unrelated
uv.lockremovals. It was closed unmerged.This branch repeats the exact fast-uri
3.1.7→3.1.9lockfile update from bot PR #2452 and the same proposed workflow as #2493, changing only the pinned component-detection action from v0.1.6 to v0.2.0 (a02aeda7a175ad4dd38a13c4d3ff2df9da8f2cf0). The upstream v0.2.0 release includes a fix for assigning detected dependencies to actual manifest and lockfile paths. Whether it removes this repository's snapshot warning is unverified.Paths and validation
.github/workflows/dependency-review.yml: same full-tree canary workflow with one verified action pin update.package-lock.json: exact fast-uri delta from fix: bump fast-uri from 3.1.7 to 3.1.9 #2452.scripts/ci/record_dependency_review.pyand workflow tests: inherited from fix: save dependency review evidence for large updates #2487/fix: match dependency snapshots on update pull requests #2492.git diff --checkpassed. The v0.2.0 tag SHA was checked against the upstream repository.Hosted diagnostic gate
This test PR intentionally references #2490 without claiming to close it, so the issue-closing metadata check may fail by design.