Repository navigation
chore: Use exact action release tags in repository workflows (#29) - #30
Conversation
|
To preview the documentation for this pull request, visit the following URL:
|
There was a problem hiding this comment.
Current status: All findings originating in this review are resolved.
Last reconciled onf725b3f. See aggregate Bugbot status.
🤖 Bugbot review snapshot
Bugbot reported 1 potential problem when commit 5aa49d5 was analyzed. This snapshot is historical; use the status block above for current state. 1 finding is linked to changed code.
Findings
- high: Mutable checkout ref runs in the OIDC publishing job —
.github/workflows/npm_release.yml:47
Bugbot: review complete
|
Copilot approval · Human review neededStatus: A protected workflow, policy, or trust-boundary file changed. Technical evidenceRevision: |
Repository-owned CI, Storybook Pages, and npm publishing workflows now reference actions by complete release tags, with a lockfile recording the corresponding commits. An architecture check enforces that the tags and recorded commits stay aligned.
What changed
Validation
Closes #29