cfrs v0.3.0-beta.11

The eleventh prerelease of cfrs, for tests.

Binaries

File	System
cfrs-x86_64-unknown-linux-musl, pod-netns-x86_64-unknown-linux-musl	Linux x86-64
cfrs-aarch64-unknown-linux-musl, pod-netns-aarch64-unknown-linux-musl	Linux ARM64
cfrs-armv7-unknown-linux-musleabihf, pod-netns-armv7-unknown-linux-musleabihf	Linux ARMv7 (32-bit, hard float)
cfrs-arm-unknown-linux-musleabihf, pod-netns-arm-unknown-linux-musleabihf	Linux ARMv6 (32-bit, hard float)
cfrs-i686-unknown-linux-musl, pod-netns-i686-unknown-linux-musl	Linux x86 (32-bit)
cfrs-riscv64gc-unknown-linux-musl, pod-netns-riscv64gc-unknown-linux-musl	Linux RISC-V 64
cfrs-loongarch64-unknown-linux-musl, pod-netns-loongarch64-unknown-linux-musl	Linux LoongArch64
cfrs-powerpc64le-unknown-linux-musl, pod-netns-powerpc64le-unknown-linux-musl	Linux POWER, little-endian

Each binary is static (musl). It needs no C library on the host. cfrs.1
is the manual page.

The image is ghcr.io/azathothas/cfrs:v0.3.0-beta.11 (also :beta).

Check a download

sha256sum -c SHA256SUMS --ignore-missing
gh attestation verify cfrs-x86_64-unknown-linux-musl --repo Azathothas/cfrs
cosign verify-blob --bundle SHA256SUMS.sigstore.json \
  --certificate-identity https://github.com/Azathothas/cfrs/.github/workflows/release.yml@refs/tags/v0.3.0-beta.11 \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com SHA256SUMS
sh scripts/rebuild.sh v0.3.0-beta.11   # rebuild and compare (x86_64, aarch64)

cfrs update from 0.3.0-beta.8 does the first three checks itself.

Breaking

None.

Fixed

• cfrs update with no --version took the first release of the GitHub
  API as the newest. The API lists the releases by tag name, so
  v0.3.0-beta.10 came after v0.3.0-beta.7. From beta.10, cfrs update
  then said that beta.9 was available, and an update went back to beta.9.
  Now cfrs takes the highest version (a release after its prereleases), and
  with no --version it never goes to an older version.
• install.sh with CFRS_VERSION=latest installed beta.9 for the same
  cause. It now takes the highest version of the list (and of
  releases.atom).

Changes for a tester

• From beta.9 or beta.10, update with the tag:

  cfrs update --version v0.3.0-beta.11

  cfrs update with no --version of these two releases does not find a
  newer release. From beta.11 on, it does.

• Each change of beta.10 is in this release: see
  docs/releases/v0.3.0-beta.10.md.

The licenses of the crates in the binaries, with their texts: THIRD-PARTY-LICENSES.md.

The commits of this release

Other

• update, install.sh: the newest release is the highest version; release v0.3.0-beta.11 (3044aa1)