Repository navigation
feat(release): apt-ready kernel packages with per-build versions, metapackages and provenance attestations - #28
Merged
Merged
Conversation
…apackages and provenance attestations Every build gets a build number (commit count, recipes/build-number.sh) in its kernel release and package versions: linux-image-7.2.10-<N>-smoothkernel at 7.2.10-<N>, linux-libc-dev and OpenZFS at -<N>. Each build installs alongside the previous kernel instead of replacing its modules, and apt sees every build as an upgrade. The DKMS module version of OpenZFS is unchanged. linux-image-smoothkernel and linux-headers-smoothkernel metapackages depend on exactly their build's packages, so systems follow new kernels through ordinary apt upgrades. The release workflow attests the build provenance of every .deb (Sigstore, public transparency log), so anyone can verify a package came from this pipeline. Signing becomes optional: unsigned releases are marked UNSIGNED.txt, run only with Secure Boot off, and are published to the apt repository like signed ones. Docs updated for smoothapt ingesting releases on the VPS.
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.
Every build gets a build number (commit count, recipes/build-number.sh) in
its kernel release and package versions: linux-image-7.2.10--smoothkernel
at 7.2.10-, linux-libc-dev and OpenZFS at -. Each build installs
alongside the previous kernel instead of replacing its modules, and apt sees
every build as an upgrade. The DKMS module version of OpenZFS is unchanged.
linux-image-smoothkernel and linux-headers-smoothkernel metapackages depend
on exactly their build's packages, so systems follow new kernels through
ordinary apt upgrades.
The release workflow attests the build provenance of every .deb (Sigstore,
public transparency log), so anyone can verify a package came from this
pipeline. Signing becomes optional: unsigned releases are marked UNSIGNED.txt,
run only with Secure Boot off, and are published to the apt repository like
signed ones. Docs updated for smoothapt ingesting releases on the VPS.
.github/workflows/release.yml | 62 +++++++++++++++++++++---------
README.md | 2 +-
docs/APT_REPO.md | 27 +++++--------
docs/CI_RELEASES.md | 73 ++++++++++++++++++++++++++++-------
docs/README.md | 2 +-
docs/RELEASE_MODEL.md | 12 +++---
docs/bumping-kernel.md | 24 +++++-------
docs/signing.md | 18 +++++----
recipes/build-kernel.sh | 88 ++++++++++++++++++++++++++++++++++++-------
recipes/build-number.sh | 30 +++++++++++++++
recipes/build-zfs.sh | 17 +++++++++
recipes/stamp-version.sh | 16 --------
12 files changed, 262 insertions(+), 109 deletions(-)