Files
wallet/doc/reproducibility.md
T
grenadeandClaude Opus 5 aa6ad55181
ci / gate (push) Successful in 12m38s
release / linux (push) Successful in 14m46s
release / package (44) (push) Successful in 39s
release / publish (44) (push) Successful in 13s
ci(release): the binary's real name, the CLI run where it finds the project
Three faults a first tag would have hit. The version check and the
collect step looked for target/release/wallet-app, but the binary has
been blackbeard-wallet since the product was renamed for packaging. The
bundle step ran the Tauri CLI with --dir ui, where there is no Tauri
project to find; it now runs from crates/wallet-app, checked with
`tauri info`, and the CLI is pinned to 2.11.4 as doc/reproducibility.md
said it would be once a release was cut. The publish job's `rpm -K`
right after signing would exit non-zero on a runner whose rpm database
does not hold the lair.cafe key; the check now runs on the repo host
after the rsync, where gitea_ci verifies cichlid-0.1.9 as OK today.

Refs #32
Refs #33

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014ftBXYuba8ARhQeF74oUgW
2026-09-16 14:25:27 +03:00

2.4 KiB

reproducibility

What the build pins, what it does not, and what a second build of the same tag is expected to differ in (blackbeard/wallet #51). The acceptance is diffoscope on two independent builds of one tag being empty, or every difference listed here with a reason. No two builds have been compared yet; this is the starting state.

Pinned

input where how
Rust toolchain rust-toolchain.toml stable with rustfmt and clippy; the runner image (runner-rust, gongfoo) carries the stable of its build date, so two builds on the same image see the same rustc. A version pin here would make rustup fetch on every run, which the runner rules forbid.
crates Cargo.lock, deny.toml --locked is implied by the lockfile in CI; cargo deny refuses unknown registries.
webview packages ui/pnpm-lock.yaml pnpm install --frozen-lockfile in CI.
node and pnpm the runner image nodejs from Fedora 44 and a global pnpm; recorded in doc/platform-smoke.md for a pass.
Tauri CLI pnpm dlx @tauri-apps/cli@2.11.4 in the release workflow exact; bumped with the tauri crates.
linuxdeploy and AppRun downloaded by the Tauri bundler into ~/.cache/tauri unpinned by Tauri; the AppImage is therefore the least reproducible artifact.
SOURCE_DATE_EPOCH the release workflow the tagged commit's time, exported to every step, so the bundlers stamp that and not the build's clock.
the version Cargo.toml, stamped into tauri.conf.json and ui/package.json script/stamp-version.sh refuses a tag that disagrees.

Expected to differ, today

  • The rpm from the Tauri bundler and the rpm from rpm/blackbeard-wallet.spec differ by construction: different spec, changelog, file list. Only the spec-built rpm is published; compare that one.
  • %changelog carries the build date through actions/rpm-changelog.
  • rustc embeds absolute paths of the build directory in debug info and panic messages; the rpm strips nothing (%__strip is disabled) so those paths survive. --remap-path-prefix is the fix and is not applied yet.
  • The AppImage embeds whatever linuxdeploy fetched that day.

Not yet done

Two builds of the same tag on two runners, and their diff. The release workflow produces the artifacts; a second run of the same tag on a different runner host and diffoscope between the two rpms is the remaining step, after the first tag exists.