Repository navigation
Release v0.2.0 - #6
Merged
Merged
Conversation
development now collects work for the next release, as in the rypt module: CI runs on pushes to it, CONTRIBUTING.md describes the main/development/feature-branch flow and the branch protection, and docs/releasing.md starts a release with a pull request into main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NTEjHbdKp83qgQgmqR1BJ6
GoReleaser now makes a CycloneDX SBOM for each binary with Syft, from the binary's build information, named like the binary and listed in SHA256SUMS. CI installs Syft, so the snapshot build checks this on every pull request. A govulncheck job fails CI when the code calls a function with a known vulnerability. Its first run found eight standard-library vulnerabilities in what Go 1.27.0 builds, which v0.1.0 and v0.1.1 were built with; Go 1.27.2 fixes them. CI and releases now build with the newest Go release, and go.mod asks for at least 1.27.2, so that "go install" users get the fixes too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NTEjHbdKp83qgQgmqR1BJ6
Run CI on development and document the branch workflow
Ship an SBOM with each binary and check for vulnerabilities
The release workflow's last step signs a SLSA build provenance attestation, with actions/attest, for every file in SHA256SUMS: each binary and its SBOM. It shows that this workflow built the file from the tagged commit, which a checksum published beside the file cannot. The README shows how to check one with "gh attestation verify". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NTEjHbdKp83qgQgmqR1BJ6
Attest the build provenance of every release file
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.
Release v0.2.0
Changes since v0.1.1:
Security
net/http, HTTP/2,crypto/tls,net/textproto) that 1.27.2 fixes. (Ship an SBOM with each binary and check for vulnerabilities #4)govulncheckCI job, now a required check, fails on any vulnerable code the CLI calls. (Ship an SBOM with each binary and check for vulnerabilities #4)Supply chain
rypt-<os>-<arch>.cdx.json), listed inSHA256SUMS. (Ship an SBOM with each binary and check for vulnerabilities #4)gh attestation verify. (Attest the build provenance of every release file #5)Behavior
github.com/x6c-co/ryptSDK v0.1.0. (Use the github.com/x6c-co/rypt module for API calls #2)rypt-cli/<version> rypt-go/v0.1.0. (Use the github.com/x6c-co/rypt module for API calls #2)Process
developmentbranch, CONTRIBUTING.md, and CI on pushes todevelopment. (Run CI on development and document the branch workflow #3)Once this is merged,
v0.2.0will be tagged on the merge commit.🤖 Generated with Claude Code
https://claude.ai/code/session_01NTEjHbdKp83qgQgmqR1BJ6