v0.42.79

Highlights

Server-signed commits now use the input commit's object hash algorithm when calculating the new commit ID.

User-visible changes

Signing paths that call the server signing function, including branch updates, buck uploads, and B3 trunk signing, preserve SHA-1, SHA-256, or BLAKE3 object IDs according to the input commit. A commit whose tree or parent references use a different hash kind is rejected through the existing error path.

Compatibility, configuration, and migration

No public API, schema, configuration, or wire-format change. No migration is required. SHA-1 commit IDs remain byte-identical for the same signing inputs. The existing author and committer policies, PGP signing algorithm, tree ID, and ordered parent IDs are preserved.

Verification

The final v0.42.79 tree passed cargo +nightly fmt --all --check, cargo clippy --all-targets --all-features -- -D warnings, source .env.test && cargo test --all (22 targets, 3,178 passed, 0 failed, 3 pre-existing ignored), cargo build, and cargo build --tests with no errors or warnings. The focused signing suite covers both identity policies, SHA-1/SHA-256/BLAKE3 with an opposing thread-local default, real PGP signature verification, and mismatched tree and parent references. Service checks used real Redis and Git signature verification.

Known limitations

This patch does not change B3 synthetic commit construction, tree reconstruction, or the full CLI/API non-SHA-1 chain. Those paths have separate planned cards and are not claimed complete by this release.