• v0.8.3 e095cb4b6a

    v0.8.3
    All checks were successful
    ci / check (push) Successful in 14m1s
    ci / live-e2e (push) Successful in 2m55s
    ci / coverage (push) Successful in 3m42s
    release / prepare (push) Successful in 3s
    release / build (catthehacker/ubuntu:act-22.04, linux-x86_64, docker, x86_64-unknown-linux-gnu) (push) Successful in 2m25s
    release / build (darwin-aarch64, macos-15, aarch64-apple-darwin) (push) Successful in 20m44s
    release / build (darwin-x86_64, macos-15, x86_64-apple-darwin) (push) Successful in 22m38s
    release / publish (push) Successful in 19s
    release / guard (push) Has been skipped
    Stable

    stephen released this 2026-11-12 12:55:27 +00:00 | 6 commits to main since this release

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

    Fixed

    • On a Fjord Account host, the git that fj runs (clone, fetch, push, pr checkout,
      stacks) no longer waits on an HTTPS username prompt. fj has no git credential for
      such a host yet (the gateway has no git route, #222), so git now runs with its
      credential prompts off (terminal, askpass programs, the credential manager's UI),
      and a failed fetch, push or clone says so and what to do: use an SSH remote, or
      give git its own credential for the instance. SSH remotes still ask for their own
      passphrase as usual. Other hosts are unchanged.
    • fj run rerun --failed on Forgejo 17 no longer reruns a job twice. It skipped a
      selected job that an earlier rerun had restarted only while that job was still
      running; a job that restarted and finished again before the next refresh was
      posted again. It now skips any selected job whose attempt changed (#306).
    • fj status filters the inbox with the mute list of the account it connected as,
      taken from the configuration the client connected with. It used to load
      hosts.toml again after connecting, so a switch from another terminal in between
      could filter one account's notifications with another account's mutes.
    • Repo-scoped commands now read hosts.toml once. Routing the clone's host, building
      the API client and working out the browser URL used separate reads, so an
      auth switch or instances use from another terminal in between could send a
      request as one account and open a page for another. repo clone, repo create and
      repo fork with --clone also take the git protocol from the host the command
      connected to (a fork of a repo on a routed host used the default host's protocol).
    Downloads