• v0.8.2 0c02ca3941

    v0.8.2
    All checks were successful
    ci / check (push) Successful in 14m33s
    ci / live-e2e (push) Successful in 3m6s
    ci / coverage (push) Successful in 3m48s
    release / prepare (push) Successful in 9s
    release / build (catthehacker/ubuntu:act-22.04, linux-x86_64, docker, x86_64-unknown-linux-gnu) (push) Successful in 4m16s
    release / build (darwin-x86_64, macos-15, x86_64-apple-darwin) (push) Successful in 6m6s
    release / build (darwin-aarch64, macos-15, aarch64-apple-darwin) (push) Successful in 6m13s
    release / publish (push) Successful in 19s
    release / guard (push) Has been skipped
    Stable

    stephen released this 2026-11-12 08:29:09 +00:00 | 11 commits to main since this release

    Signed by stephen
    SSH key fingerprint: SHA256:BdEUMiBru/dudwgzDOC0WWGznbvlf4l8Lz0bT0Gq1EE

    Fixed

    • fj workflow run no 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 optional retired list per account in hosts.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