fix(ci): pin osv-scanner-action to v2.3.3 and grant contents:write for docs#573
Merged
Merged
Conversation
…r docs Two pre-existing CI failures resolved: 1. OSV Vulnerability Scan: google/osv-scanner-action@v2 does not exist as a major-version tag. The repository only publishes specific patch versions (v2.3.3 is latest). Pinned both scan steps to v2.3.3. 2. Generate-Documentation: startup_failure caused by the reusable workflow (kcenon/common_system/.github/workflows/doxygen.yml) requiring `contents: write` permission (to deploy gh-pages) while the calling workflow had no explicit permissions block. Added `permissions: contents: write` at the workflow level so the called workflow can satisfy the permission requirement. Both failures have been occurring consistently since 2026-03-06 and are unrelated to the v0.3.0 version bump in #572.
Contributor
📊 Performance Benchmark ResultsPerformance Benchmark ReportNo benchmark data available. ℹ️ No baseline reference availableThis is the first benchmark run or baseline file is missing. |
kcenon
added a commit
that referenced
this pull request
Apr 13, 2026
…r docs (#573) Two pre-existing CI failures resolved: 1. OSV Vulnerability Scan: google/osv-scanner-action@v2 does not exist as a major-version tag. The repository only publishes specific patch versions (v2.3.3 is latest). Pinned both scan steps to v2.3.3. 2. Generate-Documentation: startup_failure caused by the reusable workflow (kcenon/common_system/.github/workflows/doxygen.yml) requiring `contents: write` permission (to deploy gh-pages) while the calling workflow had no explicit permissions block. Added `permissions: contents: write` at the workflow level so the called workflow can satisfy the permission requirement. Both failures have been occurring consistently since 2026-03-06 and are unrelated to the v0.3.0 version bump in #572.
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
1 participant
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.
What
Fix two pre-existing CI failures that have been occurring consistently since 2026-03-06.
Change Type
Why
Related Issues
Problem 1: OSV Vulnerability Scan failure
google/osv-scanner-action@v2does not exist as a major-version tag in the upstream repository. Only specific patch versions exist (latest:v2.3.3). GitHub Actions failed to resolve the action reference with:Problem 2: Generate-Documentation startup_failure
The calling workflow (
build-Doxygen.yaml) invokes the reusable workflowkcenon/common_system/.github/workflows/doxygen.yml@main, which deploys to GitHub Pages and requirescontents: writepermission. The calling workflow had no explicitpermissionsblock, causing a pre-flight permission validation failure (startup_failure) before the job could run.Both failures were pre-existing before PR #572 and unrelated to the v0.3.0 version bump.
Who
Required Approvals
When
Urgency
Where
Files Changed
.github/workflows/osv-scanner.yml@v2→@v2.3.3(both scan steps).github/workflows/build-Doxygen.yamlpermissions: contents: writeHow
Implementation Details
OSV Scanner fix: Pinned both
google/osv-scanner-action/osv-scanner-actionsteps from the non-existent@v2to the specific stable release@v2.3.3.Doxygen permissions fix: Added
permissions: contents: writeat the workflow level. This grants the called reusable workflow the permission it needs to write to thegh-pagesbranch. Without this, GitHub's pre-flight permission check fails and the job never starts.Testing Done
v2.3.3exists ingoogle/osv-scanner-actiontagsv4exists forpeaceiris/actions-gh-pages(used in callee)Breaking Changes
None.