github TheMaxMur/RS-Key v0.2.2
RS-Key v0.2.2

latest releases: v0.4.11, v0.4.10, v0.4.9...
4 months ago

[0.2.2] — 2026-06-15

No firmware change — bcdDevice stays 0x0760 and the eight .uf2 images are
bit-identical to 0.2.0. This release ships the fixed, hardened release pipeline:
0.2.0 published its GitHub Release without provenance, because the SLSA
generator's "append the provenance to the release" model is incompatible with
GitHub's immutable releases (the late asset upload is rejected — even on a draft).

Changed

  • Build provenance now uses GitHub's native attest-build-provenance, generated
    from inside a reusable workflow (release-build.yml). Running the build
    and the attestation in an isolated, identity-bound reusable workflow raises the
    release to SLSA v1 Build Level 3 (an inline attestation step alone is only
    Build L2). Each .uf2 is attested keyless (Sigstore/Fulcio + the Rekor log)
    into the attestation API instead of being uploaded as a release asset, so
    it stays compatible with immutable releases. Verify with
    gh attestation verify --signer-workflow … (docs/supply-chain.md).
  • All GitHub Actions bumped to their current major versions (off the deprecated
    Node 20 runtime).

Verify a download: https://github.com/TheMaxMur/RS-Key/blob/v0.2.2/docs/supply-chain.md

Don't miss a new RS-Key release

NewReleases is sending notifications on new releases.