Repository navigation
Conversation
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.
The dependency graph currently relies on a one-time API snapshot, which becomes stale when the lockfile changes. Add a dedicated workflow that replaces that snapshot on relevant
betapushes, with manual dispatch for retries.The job uses the pinned npm CLI's lockfile-only SBOM without installing packages, checks out the latest
betacommit to handle queued runs, and submits throughgh apiwith a step-scoped Actions token. It preserves the existing detector/correlator so the recovery snapshot is replaced. Official actions retain exact release tags.Validation: lint, strict types, build, 105 unit tests, the 90% coverage gate, 41 process tests, 16 packed runtime checks and two typed consumers passed. Parsed and checked the workflow YAML; real npm output matches all 620 packages, dependency edges and scopes in the previously verified API snapshot. An actual empty-lockfile SBOM also produces an empty snapshot.
The privileged workflow runs only on
beta; its first hosted API submission will occur after merge. The converter is covered by the normal PR test suite.