ci: grant the check job permission to publish its audit result - #204
Merged
Conversation
Every push to main has gone red since at least 85671a7, and not because anything is vulnerable — the audit reports "No vulnerabilities were found" and then rustsec/audit-check fails trying to create a check run: "Resource not accessible by integration". ci.yml declares no permissions, so the job inherits a read-only GITHUB_TOKEN. pull_request runs were unaffected, which is why this only ever showed up after a merge.
Gbemi-programmer
force-pushed
the
ci/audit-check-permissions
branch
from
August 30, 2026 16:03
74e93aa to
dbdd270
Compare
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.
Every push to
mainhas been failing —5030d26,86ab0d8,0d33d07,dce835f,85671a7— and none of them because of a vulnerability.The audit itself is clean:
rustsec/audit-check@v2publishes its result as a check run.ci.ymldeclares nopermissions:, so the job inherits a read-onlyGITHUB_TOKENand the API call is refused after the audit has already passed.pull_requestruns were unaffected, which is why this only ever showed up post-merge and never blocked a PR.Verifying
The failing path is the
pushevent, so this PR's own run cannot exercise it — a green run here only shows nothing regressed. The real confirmation is the push run onmainafter merge.Unrelated and left alone:
RUSTSEC-2024-0436(pasteunmaintained) is reported informationally and does not fail the build.