Repository navigation
👷 Automate releases with Release Drafter and reproducible builds - #1421
Merged
Merged
Conversation
Split the release build into source/compile/package targets and add `make release-container`, which compiles and packages inside a toolchain container pinned by image digest. Tarballs get normalized metadata (sorted entries, fixed mtime/owner/mode, gzip without timestamp), and VERSION can be set before a tag exists. This allows maintainers to rebuild a CI-built release bit-for-bit before signing it. Repeated builds and amd64 vs. arm64 builds produce identical checksums. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Release Drafter keeps a draft release up to date on every push to main. Pull requests are labeled by the gitmoji in their title and grouped into Features and Improvements, Security, Bug Fixes, Technical Changes and Maintenance; the next version is resolved from the labels (`breaking` for major, `enhancement` for minor, patch otherwise). A follow-up job builds the release tarballs with `make release-container` at the exact commit and attaches them, the checksums and a build-info.json to the draft. No secrets are involved; signing and publishing stay with the maintainers, who rebuild the tarballs locally first. Dependabot keeps the pinned release toolchain images up to date. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Replace bin/github-release.sh with bin/release.sh. Instead of building and uploading a release from scratch, it takes the release draft built by GitHub Actions, rebuilds the tarballs locally from the same commit in the pinned release container and only signs and publishes the release if all checksums are identical. The GPG key never leaves the maintainer's machine and GitHub's build is never signed unverified. Release notes now come from Release Drafter: CHANGELOG.md points to GitHub Releases from the next release on, and the prepare-release skill is removed. The release docs describe the new flow, the label scheme and how to debug a checksum mismatch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0x46616c6b
added
enhancement
0x46616c6b
marked this pull request as ready for review
November 3, 2026 16:52
0x46616c6b
requested review from
doobry-systemli,
t2d and
y3n4
as code owners
November 3, 2026 16:52
|
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.
Goal
Automate the release process as far as possible without handing our GPG signing key to GitHub, and without signing artifacts built by GitHub blindly.
Until now, a maintainer prepared a changelog PR (via the
prepare-releaseskill) and then ranbin/github-release.shlocally to build, sign and upload the release. With this change, GitHub drafts and builds every release, and the maintainer only verifies, signs and publishes it.How it works
main. The autolabeler labels pull requests by the gitmoji in their title. The labels decide the section in the release notes (Features and Improvements, Security, Bug Fixes, Technical Changes, Maintenance) and the next version (breakingfor major,enhancementfor minor, patch otherwise).build-info.json, to the draft. It uses onlyGITHUB_TOKEN, with no other secrets.bin/release.sh. It rebuilds the tarballs locally from the same commit and compares the checksums with the draft. Only if they are identical does it sign the checksums, create a signed tag, upload the signatures and publish the release.--dry-runonly rebuilds and compares.Reproducible builds
To make step 3 possible,
make release-containerbuilds the tarballs in a toolchain container pinned by image digest (docker/release/Dockerfile). The tarballs are created with normalized metadata: sorted entries, a fixed mtime from the commit, fixed owner and permissions, and gzip without a timestamp. Dependabot keeps the pinned images up to date.Other changes
CHANGELOG.mdis frozen at 6.12.0 and points to GitHub Releases. Theprepare-releaseskill is removed.breaking(already created) for major releases.Notes
bin/release.shcan only run for real after merge. The first release should start withbin/release.sh --dry-run.UPGRADE.mdstays manual and should be updated in the pull request that introduces the change.🤖 Generated with Claude Code