Release 2.0.0b25

[ThomasWaldmann]

See the changelog for what changed in this release.

Installation

pip install borgbackup==2.0.0b25, or use one of the standalone binaries below - they contain everything they need and just have to be made executable.

For each platform there is a single-file binary (borg-*-gh, .exe on Windows) and, as a .tgz, the same thing as a directory (borg-dir/borg.exe), which starts up faster.

The Linux binaries come in two flavours: glibc243 (built on Ubuntu 26.04) and glibc239 (built on Ubuntu 24.04) for systems with an older glibc or with a CPU below x86-64-v3, on which the glibc243 x86_64 binary does not run. Your system needs at least the glibc version in the name.

The macOS binaries are built without FUSE support, so borg mount does not work with them; install via pip instead if you need FUSE support.

All release assets have a build provenance attestation, verifiable with gh attestation verify --owner borgbackup <file>.

Every attestation is additionally attached as a sigstore bundle <asset>.sigstore.jsonl, so it can be verified offline and without a GitHub token, e.g. with cosign:

cosign verify-blob borgbackup-2.0.0b25.tar.gz \
  --bundle borgbackup-2.0.0b25.tar.gz.sigstore.jsonl \
  --certificate-identity https://github.com/borgbackup/borg/.github/workflows/release.yml@refs/tags/2.0.0b25 \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

The binaries are built by ci.yml, not by release.yml, so their --certificate-identity is https://github.com/borgbackup/borg/.github/workflows/ci.yml@refs/tags/2.0.0b25.

---

This discussion was created from the release Release 2.0.0b25.

[ThomasWaldmann]

• you need to create new repos with b25
• use ssh:// instead of rest://
• if not encrypted repos are desired: use authenticated-blake3 instead of "none"