ci: add build-provenance attestations and CodeQL scanning#33
Merged
Conversation
Two free-on-public-repos security additions pre-v1.0.0:
* release.yml — new `attest-build-provenance` step on the
goreleaser job after publish. Runs only on real releases
(dry_run=false), subject-paths cover every dist/*.tar.gz,
dist/*.zip, and dist/checksums.txt produced by GoReleaser.
Needs id-token:write + attestations:write on the job,
added to the permissions block. Keyless Sigstore signing;
no secrets required.
* codeql.yml — new workflow running GitHub's security-and-quality
Go query set on push to main, every PR, and a weekly schedule
(Mondays 06:17 UTC). Standard doc-file path-ignores so doc-only
PRs don't trip the scan.
No code change. No runtime dependency change. make check green,
coverage 100%, actionlint clean on both workflow files.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Pre-v1.0.0 security hardening — two free-on-public-repos additions:
Why now
First release (v0.9.0 dry run imminent) should already carry attestations so downstream consumers can verify provenance from day one. CodeQL findings should surface before anything is tagged.
Validation
Follow-ups after merge
Enable these via the GitHub API (one call each, not in this PR because they're settings not workflow code):