Skip to content

ci(dependencies): refresh lockfile snapshots through the api - #2

Closed
titan-ron wants to merge 1 commit into
betafrom
titan/refresh-dependency-snapshots
Closed

titan-ron wants to merge 1 commit into
betafrom
titan/refresh-dependency-snapshots

Conversation

@titan-ron

Copy link
Copy Markdown
Contributor

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 beta pushes, with manual dispatch for retries.

The job uses the pinned npm CLI's lockfile-only SBOM without installing packages, checks out the latest beta commit to handle queued runs, and submits through gh api with 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.

@github-code-quality

Copy link
Copy Markdown

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/vitest

The overall line coverage in commit 0a72bae in the titan/refresh-depend... branch remains at 95%, unchanged from commit bfe3814 in the beta branch.

@titan-ron titan-ron closed this Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant