-
v0.8.2
StableAll checks were successfulci / check (push) Successful in 14m33sci / live-e2e (push) Successful in 3m6sci / coverage (push) Successful in 3m48srelease / prepare (push) Successful in 9srelease / build (catthehacker/ubuntu:act-22.04, linux-x86_64, docker, x86_64-unknown-linux-gnu) (push) Successful in 4m16srelease / build (darwin-x86_64, macos-15, x86_64-apple-darwin) (push) Successful in 6m6srelease / build (darwin-aarch64, macos-15, aarch64-apple-darwin) (push) Successful in 6m13srelease / publish (push) Successful in 19srelease / guard (push) Has been skippedreleased this
2026-11-12 08:29:09 +00:00 | 11 commits to main since this releaseFixed
fj workflow runno longer fails with "could not find the triggered run" after a
successful dispatch. Forgejo reports an empty event for dispatched runs, which the
run lookup did not accept (#321).- The Fjord Account web-fallback refusal no longer says the gateway "does not forward"
web routes. fj never sends an imported browser session cookie on any request; the
cookie stays stored and listed only. - Replacing a profile (PAT login,
auth refresh --token, Fjord login) now deletes
the previous generation's stored credential. If the delete fails, the replaced
generation is kept in a new optionalretiredlist per account inhosts.toml
(older files load unchanged), the command reports it, and the next login,
refresh or logout on that host retries until it is gone. A staged credential
whose own cleanup fails is listed the same way when its host already has
named profiles. Deleting from a keychain that cannot be reached (Linux, or
FJ_NO_KEYCHAIN=1) is not confirmed, as for logout.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads