Release v0.8.1 #315
Loading…
Reference in a new issue
No description provided.
Delete branch "release-v0.8.1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Release v0.8.1, mirroring #312. I do not tag; the lead does after merge.
Changes: Cargo.toml and Cargo.lock to 0.8.1, README badge and install URLs, CHANGELOG [Unreleased] moved under [0.8.1] (2026-11-11). The entries were already written by the PRs below.
Covered since v0.8.0: #313
fj release downloadthrough the gateway on Fjord Account hosts (#222); #314 logout and session clear report keychain delete failures (CLS-1267 item 3).The cookie-slot fix the lead listed (self-review (b) of #311) needs no change: it was raised against ebdd47f, and the merged code derives cookie slots from host and account only, so rotation and re-login do not move them. Existing coverage: tests/profile_maintenance.rs replaces a cookie after a token rotation and checks only one secret remains.
Release preflight: not run from this checkout (this host has no rasterhub.com runner scope). The lead checked runners (3 macos-15 idle, 2 docker active) and release secrets for v0.8.0. Version in Cargo.toml matches v0.8.1;
cargo check --lockedpasses.Self-review of
9b34a2b: no findings, BLOCKING 0.Automated Codex review (read-only) of head
9b34a2b0e0.No real findings. Version metadata, install URLs and changelog match the release workflow. Checked against STANDARDS.md; no builds or network access performed.
BLOCKING: 0
Reviewed head
9b34a2b0e0at 2026-11-11T16:31:31Z by codex exec (read-only sandbox).