Repository navigation
Publish signed installer checksums with every release - #558
Merged
Merged
Conversation
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
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.
publish.yml (runs for every published release, RC and stable) now attaches two assets to the GitHub Release:
SHA256SUMS: sha256 ofdeploy/deploy.yamlanddeploy/crd.yamlat the tag, one line each, named by that repo path (<sha> deploy/deploy.yaml). Hashed fromgit show <tag>:<path>, the bytes raw.githubusercontent.com serves, so kwatch.sh can verify what it fetches.SHA256SUMS.sigstore.json: cosign keyless bundle, same identity as the existing release checksums (issuerhttps://token.actions.githubusercontent.com, identity^https://github.com/abahmed/kwatch/.github/workflows/publish.yml@).verify_published_artifactsdownloads both, verifies the bundle, then fetches the two files from raw at the tag and runssha256sum -c. The existingkwatch-<tag>-SHA256SUMSevidence and release.json schema are unchanged; the release notes link the new files.Not done: pinning the deploy.yaml image by digest. The tag (and its deploy.yaml) is created by release.yml before publish.yml builds the image, so the digest does not exist yet at tag time; pinning would mean retagging or a post-build commit.
First release with the assets: v1.0.0-rc.20. actionlint and check-release-consistency pass locally; the workflow path only runs on a real release.