v0.1.1

Website · Documentation · Quick start · Desktop guide

Patch release containing the pre-publication fixes and dependency security updates.

Fixed

• Desktop export resolves directory aliases before checking for overlap,
  refuses destination links and stale files, and replaces existing hardlinks
  without modifying their other copies. Interrupted exports can still resume.
• Failed key generation removes the newly created unmatched private key;
  multiline key comments are rejected and key-file write errors are reported.
• DCO checks fail when commit history cannot be read and require a real Git
  trailer rather than a sign-off quoted in a commit message.
• The air-gap demo uses a fresh output folder and refuses nonempty custom
  destinations instead of recursively deleting them; custom output paths now
  receive the binary built for that run.

Security

• Require Go 1.26.8 and update CIRCL, compression, and Go crypto/text/network
  dependencies to address published vulnerabilities.
• Add Linux and Windows vulnerability scans for both modules on pull requests,
  pushes, and a weekly schedule.
• Ignore common private-key files, local environment files, and bundle outputs
  to reduce accidental publication of operator data.

Changed

• Reorganized the README and user documentation around installation, signed
  bundle workflows, platform setup, CLI reference, and troubleshooting.
• Updated desktop build instructions for the single repository containing both
  Go modules, and clarified desktop versus CLI requirements.
• Refreshed contribution and support guidance, issue forms, and pull request
  expectations; collected validation gaps in a dedicated status page.

Full changelog: v0.1.0...v0.1.1

---

Artifacts. debark_* is the CLI: Linux amd64/arm64 and Windows amd64 archives, plus .deb and .rpm packages. debark-gui_* is the desktop application, published onto this same release from this same tag. There are no macOS builds.

Verifying. debark_checksums.txt covers every CLI artifact and is signed with cosign in keyless mode; debark_checksums.txt.sig and debark_checksums.txt.pem are its signature and certificate. The desktop app has its own debark-gui_checksums.txt. Check each artifact against the file for its own product — sha256sum -c --ignore-missing against the wrong one exits 0 having verified nothing.

debark v0.1.1 — Apache-2.0, forever. No telemetry, no analytics, no update check, in any edition. See docs/free-paid-policy.md for exactly what stays free.

---

Desktop application (debark-gui)

Linux/amd64 is the supported target. The Windows build is provided because it compiles, not as a support commitment, and it carries no icon and no DPI manifest. There is no macOS build and none is planned.

Verify these artefacts against debark-gui_checksums.txt (cosign-signed; .sig and .pem beside it), not against the CLI's debark_checksums.txt — sha256sum -c --ignore-missing against the wrong file exits 0 having checked nothing.

Debark v0.1.1 — Apache-2.0. No telemetry, no analytics, no crash reporting and no update check, by construction: see gui/docs/dependency-review.md. This application never contacts a debark-operated endpoint; the only hosts it reaches are the distro archives named in the target's own sources and vendor .deb URLs the operator typed.

PROVENANCE.txt inside each archive names the exact debark engine commit this build was linked against — which, now that the engine and the desktop app live in one repository, is this release's own commit. gui/docs/release.md explains what is and is not reproducible here — in particular that the Linux binary's reproducibility is conditioned on the build image, because it links GTK3 and WebKitGTK through cgo.

v0.1.0

Changelog

• 603317f debark: move Debian/Ubuntu software across an air gap, and prove it

---

Artifacts. debark_* is the CLI: Linux amd64/arm64 and Windows amd64 archives, plus .deb and .rpm packages. debark-gui_* is the desktop application, published onto this same release from this same tag. There are no macOS builds.

Verifying. debark_checksums.txt covers every CLI artifact and is signed with cosign in keyless mode; debark_checksums.txt.sig and debark_checksums.txt.pem are its signature and certificate. The desktop app has its own debark-gui_checksums.txt. Check each artifact against the file for its own product — sha256sum -c --ignore-missing against the wrong one exits 0 having verified nothing.

debark v0.1.0 — Apache-2.0, forever. No telemetry, no analytics, no update check, in any edition. See docs/free-paid-policy.md for exactly what stays free.

---

Desktop application (debark-gui)

Linux/amd64 is the supported target. The Windows build is provided because it compiles, not as a support commitment, and it carries no icon and no DPI manifest. There is no macOS build and none is planned.

Verify these artefacts against debark-gui_checksums.txt (cosign-signed; .sig and .pem beside it), not against the CLI's debark_checksums.txt — sha256sum -c --ignore-missing against the wrong file exits 0 having checked nothing.

Debark v0.1.0 — Apache-2.0. No telemetry, no analytics, no crash reporting and no update check, by construction: see gui/docs/dependency-review.md. This application never contacts a debark-operated endpoint; the only hosts it reaches are the distro archives named in the target's own sources and vendor .deb URLs the operator typed.

PROVENANCE.txt inside each archive names the exact debark engine commit this build was linked against — which, now that the engine and the desktop app live in one repository, is this release's own commit. gui/docs/release.md explains what is and is not reproducible here — in particular that the Linux binary's reproducibility is conditioned on the build image, because it links GTK3 and WebKitGTK through cgo.