-
v0.8.4
StableAll checks were successfulci / check (push) Successful in 28m11sci / live-e2e (push) Successful in 4m43sci / coverage (push) Successful in 6m1srelease / prepare (push) Successful in 7srelease / build (darwin-x86_64, macos-15, x86_64-apple-darwin) (push) Successful in 5m33srelease / build (darwin-aarch64, macos-15, aarch64-apple-darwin) (push) Successful in 5m38srelease / build (catthehacker/ubuntu:act-22.04, linux-x86_64, docker, x86_64-unknown-linux-gnu) (push) Successful in 10m34srelease / publish (push) Successful in 26srelease / guard (push) Has been skippedreleased this
2026-11-18 18:09:31 +00:00 | 2 commits to main since this releaseFixed
fj workflow runasks Forgejo for the run its dispatch created (return_run_info)
and reports that run, instead of searching the newest runs for one that looks new.
The search could miss the run on a busy repository, where other runs push it off
the first page before it is listed, and print "could not find the triggered run"
for a dispatch that succeeded; it also could not tell two dispatches of one
workflow apart. A server that does not return run info still gets the search.- The subprocess tests set
FJ_CONFIG_DIR, so on macOS (which ignores
XDG_CONFIG_HOME) they no longer read the developer's realhosts.toml. Both
changes are from Peter Swimm (Toilville LLC). - Updated
quinn-udpto 0.5.16 for RUSTSEC-2026-0538 (#329).
Thanks to Peter Swimm (Toilville LLC) for the workflow dispatch run lookup and the hermetic macOS test fix.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
1 download
-
v0.8.3
StableAll checks were successfulci / check (push) Successful in 14m1sci / live-e2e (push) Successful in 2m55sci / coverage (push) Successful in 3m42srelease / prepare (push) Successful in 3srelease / build (catthehacker/ubuntu:act-22.04, linux-x86_64, docker, x86_64-unknown-linux-gnu) (push) Successful in 2m25srelease / build (darwin-aarch64, macos-15, aarch64-apple-darwin) (push) Successful in 20m44srelease / build (darwin-x86_64, macos-15, x86_64-apple-darwin) (push) Successful in 22m38srelease / publish (push) Successful in 19srelease / guard (push) Has been skippedreleased this
2026-11-12 12:55:27 +00:00 | 6 commits to main since this releaseFixed
- On a Fjord Account host, the
gitthat 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 --failedon 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 statusfilters 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.tomlagain 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.tomlonce. Routing the clone's host, building
the API client and working out the browser URL used separate reads, so an
auth switchorinstances usefrom another terminal in between could send a
request as one account and open a page for another.repo clone,repo createand
repo forkwith--clonealso 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
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
8 downloads
- On a Fjord Account host, the
-
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
-
v0.8.1
StableSome checks failedci / check (push) Has been cancelledci / coverage (push) Has been cancelledci / live-e2e (push) Has been cancelledrelease / prepare (push) Successful in 3srelease / build (catthehacker/ubuntu:act-22.04, linux-x86_64, docker, x86_64-unknown-linux-gnu) (push) Successful in 4m1srelease / build (darwin-aarch64, macos-15, aarch64-apple-darwin) (push) Successful in 6m1srelease / build (darwin-x86_64, macos-15, x86_64-apple-darwin) (push) Successful in 6m1srelease / publish (push) Successful in 1m0srelease / guard (push) Has been skippedreleased this
2026-11-12 01:03:54 +00:00 | 18 commits to main since this releaseFixed
- Logging out and clearing a web session no longer report success when the OS
keychain refuses access (locked or denied) and may still hold the secret: the
file entry is removed, the command fails, and running it again finishes the
job. Where keyutils is blocked on Linux (a container with the default seccomp
profile), logout still succeeds, with one warning that the keychain entry could
not be confirmed removed. fj release downloadon a Fjord Account host fetches release assets through the
gateway with the Fjord session instead of an unauthenticated request to the
forge's web origin, which answered 404 for a private repository. The asset URL
must be the exact download route of the release being downloaded; anything else
is refused.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- Logging out and clearing a web session no longer report success when the OS
-
v0.8.0
StableAll checks were successfulci / check (push) Successful in 16m45sci / coverage (push) Successful in 4m48sci / live-e2e (push) Successful in 4m58srelease / prepare (push) Successful in 6srelease / build (darwin-aarch64, macos-15, aarch64-apple-darwin) (push) Successful in 6m50srelease / build (darwin-x86_64, macos-15, x86_64-apple-darwin) (push) Successful in 6m54srelease / build (catthehacker/ubuntu:act-22.04, linux-x86_64, docker, x86_64-unknown-linux-gnu) (push) Successful in 7m23srelease / publish (push) Successful in 1m17srelease / guard (push) Has been skippedreleased this
2026-11-11 16:27:42 +00:00 | 21 commits to main since this releaseAdded
- Account overrides and named profiles (#157, #307, #308, #309, #310, #311).
fj --account <login>(orFJ_ACCOUNT) runs one command as a named account
without touching stored credentials. For a PAT host it pairs withFJ_TOKEN
or a host-scoped variable, and the login is verified against/userbefore
any other request goes out. With an override active, fj refuses every other
way a request could pick its identity (stored, anonymous and web-session
fallbacks, custom auth headers,Sudo, and tokens in the URL or form body).
fj auth login --account <name>stores verified PAT and Fjord OIDC profiles
per host and account, with an explicit default. Fjord instances, browser
shortcuts, mute and inbox filtering,fj statusand thefj workdisplay
follow the selected account.fj auth token,refresh,sessionand
logoutwork per profile, and session cookies are stored per profile. No
command sends a stored profile cookie yet. Usage is in
docs/account-override.md. Behavior without--accountis unchanged. fj run rerunon Forgejo 17 (#305).fj run rerun <n> [--failed | -j <job>]uses the token-accepting rerun endpoints, so it works with an API
token on private repositories.fj pr edit --base <branch>. The base is sent only when this flag is
given (#302).
Fixed
- Validate artifact downloads and zip release assets before reporting success.
Retry incomplete bodies up to three attempts and install downloads atomically
(#298). fj run view --log-failedkeeps the logs that loaded. One job with a
missing or failed log no longer fails the whole command. Each job is settled
on its own, and a failed read exits non-zero after printing (#300).fj run logsfinds the run's task. Jobs are matched by task id, the task
list is paged, and a run far back in a busy repository is found by
bisection instead of reading as an incomplete list (#301, #303).fj pr editnever moves the base of a pull request. The shared edit
path reads the base back and restores it, with an error, if the server
changed it (#302).- A late Fjord refresh answer no longer replaces a newer stored refresh
token. The stored record is checked again before the answer is saved (#302).
Security
- rustls-webpki 0.103.16, webpki-roots 1.0.11 and tokio 1.54.1. Picks up
the fixes for RUSTSEC-2026-0381, RUSTSEC-2026-0382 and RUSTSEC-2026-0386
(#299). - rustix 1.1.6. Picks up the fix for RUSTSEC-2026-0486, unsound handling
of extended-attribute buffers. - One account per command. Account overrides and profile routing cannot
fall back to another stored identity, and a pinned repository with an
unparseable remote fails instead of using another host (#307, #310). cargo auditignores RUSTSEC-2026-0374 (basic-tomlunmaintained), which
comes through theuniffichain already tracked as debt (#296).
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- Account overrides and named profiles (#157, #307, #308, #309, #310, #311).
-
v0.7.0
StableAll checks were successfulci / check (push) Successful in 11m32sci / coverage (push) Successful in 2m14sci / live-e2e (push) Successful in 2m52srelease / prepare (push) Successful in 4srelease / build (catthehacker/ubuntu:act-22.04, linux-x86_64, docker, x86_64-unknown-linux-gnu) (push) Successful in 4m4srelease / build (darwin-aarch64, macos-15, aarch64-apple-darwin) (push) Successful in 4m49srelease / build (darwin-x86_64, macos-15, x86_64-apple-darwin) (push) Successful in 5m0srelease / publish (push) Successful in 21srelease / guard (push) Has been skippedreleased this
2026-10-20 17:04:57 +00:00 | 37 commits to main since this releaseAdded
fj runner token. Prints an Actions runner registration token and
nothing else, so provisioning can run
forgejo-runner register --token "$(fj runner token --org ORG)". Scope is
the repository (-R, or the current clone) by default, or--org,--user
or--instance(instance administrators only).
Fixed
fj pr readyclears the draft state. Forgejo and Gitea compute "draft"
from a work-in-progress title prefix and ignore adraftfield on edit, so
the old{"draft": false}PATCH reported success and changed nothing.
fj pr readynow removes theWIP:or[WIP]prefix from the title and
confirms against the response that the pull request is no longer a draft. It
says so when the pull request was already ready, and fails with the fix
when the title carries a prefix only the instance knows about.fj stack sync --readyshares the path.fj pr create --draftandfj stack sync --draftopen a draft. The
draftfield they sent on create was ignored for the same reason. They now
prefix the title withWIP:unless it already has a recognised prefix.- Ctrl+C exits 130 on the graceful path. Only the forced backstop used the
conventional status; an interrupt the command loop caught itself exited 1. fj issue listandfj issue createexplain a repo without a built-in
tracker. A repo that keeps issues in an external tracker, or has them
switched off, answers 404 on the issue routes, which read as "not found:
owner/repo". The message now names the cause and the external tracker URL.
The exit status is still 3.- The Homebrew formula test matches real output. It looked for the short
description infj --help, which prints the long one. It now readsfj -h. - Run commands find runs older than the newest 50.
fj run view,--log,
--log-failed,rerun,canceland artifact downloads resolve a run number
through the run list, and that read never left the first page because Forgejo
sends noLinkheader there. An older run in a busy repository was reported
as not found. The lookup now asks the server for the run number directly, and
fj run list --paginatefollowstotal_count, so it returns every page too.
fj run view --log-failedon a run with nothing failed says so (#248).
Security
- rustls 0.23.46. Picks up the fixes for RUSTSEC-2026-0346 through 0349,
which include a ServerHello that could downgrade later connections to
classical key exchange andDebugoutput that exposed TLS session secrets.
Downloads
-
Source code (ZIP)
2 downloads
-
Source code (TAR.GZ)
33 downloads
-
v0.6.0
StableAll checks were successfulci / check (push) Successful in 11m47sci / coverage (push) Successful in 2m30sci / live-e2e (push) Successful in 2m40srelease / prepare (push) Successful in 10srelease / build (catthehacker/ubuntu:act-22.04, linux-x86_64, docker, x86_64-unknown-linux-gnu) (push) Successful in 2m58srelease / build (darwin-aarch64, macos-15, aarch64-apple-darwin) (push) Successful in 5m45srelease / build (darwin-x86_64, macos-15, x86_64-apple-darwin) (push) Successful in 5m54srelease / publish (push) Successful in 19srelease / guard (push) Has been skippedreleased this
2026-10-11 23:52:08 +00:00 | 45 commits to main since this releaseAdded
- Notifications can be handled one thread at a time.
fj status read <ID>
marks a single thread read and confirms it against the server.
fj status unsubscribe <ID>drops your subscription to the issue or pull
request behind a thread and marks it read; a thread with no work item behind
it is refused before anything is sent.fj status mute|unmute|mutedkeep a
per-account list of repositories to hide from the inbox (stored in
muted_repos.tomlnext tohosts.toml), with--include-mutedto see them
anyway. Muted threads still count toward the server's unread count. fj issue reaction,fj issue dependencyandfj issue time. Reactions
(list|add|remove|toggle) work on an issue or pull request body or, with
--comment, on one comment. Dependencies (list|add|remove) show "Depends
on" and "Blocks" as two lists and keep the direction through--blocks; a
self reference, a duplicate and a cycle are refused before any mutation.
Tracked time (list|add|delete) logs and totals time, reading durations as
1h30m,45m,90sor1:30. All three accept a pull request number.fj issue list --sortandfj issue create --milestone.--sorttakes
Forgejo's own orders (recentupdate,leastupdate,latest,oldest,
mostcomment,leastcomment,nearduedate,farduedate).--milestone
takes a title or an id and errors on an ambiguous title.fj issue view --jsonand the list JSON gain amilestonefield.- Inline review comments. `fj pr review N --line-comment ` is repeatable, and `--line-comments-file` takes the same as a JSON array. `LINE` is `N` or `new:N` for the pull request's version of the file and `old:N` for a removed line. Comments given with `--event` go out in that review in one request; without `--event` they post as a plain comment review. Each anchor is checked against the diff first, so a line that cannot be commented on is refused locally with the commentable lines named.
fj pr mergeexplains a blocked merge before it tries. It reads the base
branch's effective protection, which needs read access only, and stops on a
certain blocker (a required check failing, pending or not reported, a missing
required approval, no merge permission) with the reason. Evidence it could
not read stays "unknown" and never blocks.fj pr checksshows the same
verdict, gains aREQUIREDcolumn, and lists required checks that have not
reported; its--jsongainsrequired,statuses_completeand
merge_preflight.- Organizations and teams.
fj org createcreates an organization.
fj org team create|members|add-member|remove-member|repos|add-repo| remove-repomanage a team; every change is followed by a read, and the
command errors if that read contradicts it. - Repository transfers.
fj repo transfer requestresolves the new owner
and refuses an unknown owner, the current owner and an already pending
transfer before it asks.fj repo transfer list|view|accept|rejectreview
incoming transfers. Forgejo has no incoming-transfer endpoint, solist
scans your repository listings and can miss a transfer addressed to one of
your organizations;view -Ralways works. fj repo topics add|removechange single topics and print the list the
forge confirms.- Commits and files at a ref.
fj repo commit list|viewread history at
--ref,--branchor--tagand show each commit's signature state.
fj repo contents [PATH]reads a file or directory at a ref, with a tag
pinned to its commit.fj browse --tagopens the tag route. - Organization labels and exclusive groups.
fj label list|create|edit| delete --org ORGwork on organization labels, with--exclusiveand
--no-exclusiveforgroup/namelabels. Assigning labels on issue and pull
request create or edit falls back to the organization's labels for names the
repository does not have. fj admin.fj admin settingsandfj admin cron listare read-only
views of the instance.fj admin user createtakes the password from stdin
or a prompt, never from a flag, and keeps it out of--debug.
fj admin unadopted list|adopt|deletehandle unadopted repositories behind a
typed confirmation. A 403 reads as "requires an instance administrator" and
is never folded into "unavailable".fj profile.fj profile view|edit,fj profile email list|add|remove
andfj profile avatar set|delete. An edit sends only the fields that were
passed and warns about any the response does not reflect.- Account groups.
fj auth group list|create|rename|delete|assign|unassign
keep user-named groups of hosts inhosts.toml. Grouping never changes host
resolution.fj auth statusandfj auth listshow the group once one
exists. - The Commons appears in
fj instances. A joined Commons is listed beside
the account's own forges: selectable when the gateway can route to it, and a
"browser only" row otherwise, whichfj instances use commonshands off to
the browser. The lookup is best-effort, so a slow or failing Commons no
longer fails the listing. - Forge flavor detection and capability gates. fj identifies Forgejo or
Gitea before applying a version floor, stores the flavor and version at
login and refresh, and shows them infj auth status. One table decides
which routes are offered.fj run rerunuses the Gitea 1.26+ routes and
fj run cancelthe Forgejo 16 route; a withheld action sends nothing and
names the run URL. - Basic-auth reverse proxies.
fj auth proxystores a separate HTTP Basic
credential for a proxy in front of the forge. A 407 proxy takes it in
Proxy-Authorization. A 401 Basic proxy takes it inAuthorization, and
the forge token moves toX-Forge-Authorization, which the proxy has to
forward.--pat-transport queryworks with an unmodified proxy at the cost
of the token appearing in access logs. Git over HTTPS behind such a proxy is
out of scope; use SSH.
Changed
- The
fj statustable has a leadingIDcolumn, which shifts the columns
for anything parsing the table.--limitabove 50 now pages instead of
silently clamping. fj label create|edit --coloris now--label-color. The old flag
shared an id with the global ANSI--colorand both commands panicked at
parse time, so the old spelling never worked.fj variable listoutput changed. The table isNAME / VALUE / SCOPE
and the JSON follows the forge'sActionVariableshape (name,data,
owner_id,repo_id).fj instances list --jsongainskind,routingand acommons
descriptor. A browser-only Commons entry has a nullid.- The token no longer reaches any web route. Job logs are read through the
Actions API with ranged requests (1 MiB chunks, 64 MiB ceiling).fj run view,fj run watchand artifact downloads use the API where the server
has it and fall back to an anonymous web request elsewhere, so on older
servers they work for publicly readable runs only. fj run rerunon Forgejo reports that the forge has no rerun route
instead of attempting a web POST that could never succeed with a token.- A Fjord Account re-login re-validates the remembered instance. It is kept
when still present and ready; otherwise it is cleared and the ready
instances are printed with thefj instances use <id>hint. fj pr review --event commentwith nothing to say, and--event request-changeswith no body, fail locally instead of as a server 422.fj repo topics --setprints the list the forge confirms and validates
topic names locally.
Fixed
- Concurrent commands no longer sign a Fjord Account out. The refresh token
rotates on every exchange and a replay revokes the whole family, so two
commands refreshing at once (a prompt hook plus an interactive command is
enough) killed the session. Refreshes now take a per-platform file lock held
across the exchange and the persist, and the rotated refresh token is written
before the new bearer, so an interruption leaves the previous pair intact. A
spent grant now prints the recovery as the first line of the error. fj auth login --fjordkeeps the selected instance. Signing in again to
a platform you were already signed into cleared the default instance, so the
command after a successful recovery failed with "no default Fjord instance
selected".fj pr mergeno longer blames a required check on a green pull request.
Forgejo treats each required status context as a glob, so*means every
reported context. fj looked the pattern up by name, never found a check
called*, and reported it missing. Patterns are now matched the way
Forgejo matches them, and a failing check is reported under its real name.fj repo collaborator listreported every permission as none. The list
endpoint sends no permissions, so each row is now resolved through the
per-collaborator endpoint; a row that cannot be read shows "unknown".fj variable setcould not create a variable, and a non-emptyfj variable listfailed to decode.setnow creates or replaces and confirms.
Variable values no longer reach--debugoutput.- fj warned "older than Forgejo 7" on any Gitea 1.x host. The version floor
now applies to Forgejo only. fj issue time listprinted its total on the last row of the table.
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
6 downloads
- Notifications can be handled one thread at a time.
-
v0.5.0
StableAll checks were successfulrelease / prepare (push) Successful in 4srelease / build (catthehacker/ubuntu:act-22.04, linux-x86_64, docker, x86_64-unknown-linux-gnu) (push) Successful in 2m20srelease / build (darwin-aarch64, macos-15, aarch64-apple-darwin) (push) Successful in 3m55srelease / build (darwin-x86_64, macos-15, x86_64-apple-darwin) (push) Successful in 3m44srelease / publish (push) Successful in 20srelease / guard (push) Has been skippedci / check (push) Successful in 11m6sci / live-e2e (push) Successful in 2m8sci / coverage (push) Successful in 2m30sreleased this
2026-09-13 18:32:57 +00:00 | 52 commits to main since this releaseAdded
fj stack shiprestacks the rest of the stack after a squash land. A
squash merge replaces the item's commits, so every branch above it was left
parented on history the trunk no longer had: the PRs above showed the landed
diff a second time and the stack had to be repaired by hand. Ship now replays
the remainder onto the new trunk tip with a single
git rebase --onto <new trunk> <landed tip> <top branch> --update-refs(the
plumbingstack absorbalready used), force-pushes each branch with an
explicit--force-with-lease, and re-syncs the PR bases. A conflicting
replay rolls the rebase back and force-pushes nothing, then ship stops with
the commands to finish by hand. The PR directly above the landed item is
still re-pointed at the trunk, because the base branch it was targeting has
merged away and leaving it aimed at a deleted branch would be worse than the
no-restack end state. Merge-commit lands are unaffected, since the original
commits stay reachable.--no-restackopts out. The replay needs git 2.38 or
newer.fj stack shippre-flights the stack's shape in git. Before merging
anything it verifies that each unmerged branch descends from the one below
it, that the lowest one contains the trunk's fetched tip, and that each
local branch tip matches the head of the PR that would merge. A stale or
non-linear stack is refused up front with a "restack, thenfj stack sync"
message rather than failing mid-merge with the bottom already landed.fj stack shipre-validates between merges. After an item lands, the
next one is re-checked (still open, still mergeable, still approved, still at
the head fj most recently put there) before it is merged. If the ground
shifted, ship stops cleanly, reports what already landed, and leaves the rest
for a re-run. Checks that ship itself re-armed by force-pushing a restacked
branch are not re-gated. A forge still serving the pre-restack head is a
lagging read rather than a shift, so ship re-reads a few times; if it never
catches up, that is a stop in its own right, since every field on that
snapshot describes a shape the restack has already replaced.stack ship --jsonnow reports the branches restacked after each item
(restacked), andstack review --jsoncarries each PR's head sha
(head_sha). Both fields are additive.fj run logsprints Actions job logs. The singularfj run logstays as
an alias, so existing invocations keep working. A personal access token is
enough for log reads on this Forgejo build; the auth docs no longer claim a
browser session cookie is required. A session is still needed for the
cookie-gated web routes,run watch,run rerun, andrun cancel.fj instanceslists the Fjord Commons.fjread only
/me/forge-instances, which by design excludes the Commons, so there was no
instance id to address and no way to reach it. The Commons is now read
alongside your own instances and routed through the platform gateway, with no
personal access token anywhere: the gateway mints the forge token server-side
and nothing minted reaches the client. A Commons you have not joined is
withheld frominstances usebut still named infj instances, on a dimmed
line, so "not joined" does not read as "no such forge".- Host-scoped
FJ_TOKEN_<HOST>andFJ_SESSION_<HOST>. The host suffix is
Hfollowed by the uppercase hex of the host bytes, sorasterhub.comis
FJ_TOKEN_H7261737465726875622E636F6D. The encoding is injective, so
foo-bar.comandfoo.bar.comcannot collide onto one variable, and CI can
set a credential for one host without enumerating the rest. fj pr merge --style fast-forward-only. Forgejo's fast-forward-only
merge style is accepted both as an explicit--styleand as a repository's
default_merge_style, which previously failed as unsupported. A PR that is
not a fast-forward onto its base is reported as such, with the rebase to do,
instead of a raw forge error.
Changed
fj pr mergefollows the repository's default merge style. An omitted
--styleresolved tomergeregardless of how the repository was
configured, so merging from the CLI could produce a merge commit on a repo
whose web UI squashes. It now reads the repository'sdefault_merge_style,
and fails explicitly if that cannot be read or is not a style fj supports
rather than falling back to a guess. Scripts that relied on the implicit
mergeneed--style mergespelled out. Merge-style is also reported in
push-rejection diagnostics, so a signed-commit protection failure is no
longer misread as something else.- A generic
FJ_TOKENis no longer sent to a host it was not meant for.
It used to be picked up for any host. It is now accepted for the default or
current host, including when you spell that same host with--host, and
ignored when--hostnames a different configured host. Use
FJ_TOKEN_<HOST>for that case.FJ_SESSIONfollows the same rule. - The default Fjord platform URL is
https://fjord.sh, replacing the old
preview URL. An HTML response on a platform call now names--platform-url
instead of surfacing an opaque JSON decode error. - Global
--hostreaches the auth subcommands.fj auth status,token,
refresh,session,logout, andsetup-gitnow honor it, so
fj auth status --host Xreports hostXalone.
Fixed
-
cargo test --allnow passes on macOS. Four defects kept it from
finishing there, and each one was a test reading the developer's real machine
instead of its own scratch state.ProjectDirsignoresXDG_CONFIG_HOMEon
macOS, so tests that thought they had redirected the config directory were
loading the realhosts.toml; when that named a host whose token lives in the
login keychain, the lookup then blocked forever in securityd, because a
keychain item's ACL names the binaries allowed to read it and a freshly built
test binary is not one of them.FJ_CONFIG_DIRandFJ_NO_KEYCHAINgive
those tests, and any scripted run that wants its own state, a way to say so.
The editor test hardcoded/bin/false, which exists on Linux but not on
macOS, so it asserted on a spawn failure rather than the nonzero exit it was
written for. And the loopback sign-in test drove real sockets on a paused
clock, which cannot work: tokio's auto-advance does not wait for socket
readiness, so it jumped the clock past the five-minute callback deadline while
the silent connection was still in the accept queue. That one now runs on the
real clock with the request-line bound shortened for the test; the shipped
ten-second bound is unchanged. -
The pager no longer swallows short, write, and machine output. The
decision to page was made per top-level command family, so every subcommand
underrepo,issue,pr,release,label,milestone,tag,run,
search,status, andapiwas piped intoless, including one-line write
confirmations (pr merge,issue close,repo star,tag create, ...),
fixed status blocks (fj status,fj pr status), short reads (tag view,
milestone view,repo topics), and every--jsonand--webinvocation.
Destructive commands that prompt for confirmation (repo delete,
release delete,tag delete) were prompting on a stdout already redirected
into the pager. Paging is now decided per subcommand by
cli::paging::should_page, which pages only genuinely long read-only views:
list and view commands,pr diff/commits/files/checks,
run log,search, andfj apiGET dumps.--no-pager,FJ_NO_PAGER,
FJ_PAGER/PAGER, and the non-TTY check are unchanged. -
fj pr mergeno longer discards the pull request description. With no
--message, fj sent an empty merge-commit body, and Forgejo does not fall
back to the description the way its web merge dialog does. Every pull request
merged through the CLI therefore landed with its body gone, silently: the
merge succeeded and the commit looked normal. The message now defaults to the
pull request body. An explicit--messagestill wins, and--message ""
still produces a deliberately empty body. -
Ctrl+C works when fj is blocked in a synchronous call. SIGINT was raced
against the command future, so it only took effect while that future was
still pollable. Several paths parked the thread inside a blocking syscall for
an unbounded time, and because tokio had already replaced SIGINT's default
disposition the signal did not terminate the process either: Ctrl+C was not
slow, it was inert. The two confirmed states were an OS keychain read waiting
on an authorization dialog it cannot present (over ssh, in CI, from a git
hook, which is what deadlocked the pre-push hook) and the synchronous stdin
reads behind--body -,--input -,--with-token, and the interactive
Fjord Account prompts. A backstop now gives the graceful path 250 ms to
unwind and then exits 130. A child that owns the terminal's foreground
process group still gets to decide what SIGINT means, solessabsorbing it
is unaffected. -
Ctrl+C exits during an OIDC sign-in.
fj auth loginwaited for the
loopback redirect on a blocking task, so an interrupted sign-in printed
error: interruptedand left the process alive. The wait is now async and
actually cancellable. A stalled connection no longer wedges the sign-in
either: a socket that connected and sent nothing (a browser preconnect, a
port scanner) blocked the accept loop forever and the real redirect behind it
was never served. Request lines are now bounded at 10s, and the overall 300s
budget also covers connection handling. -
FJ_TOKENno longer blocksfj auth login --fjord. The variable was
bound to--tokenby clap, so having one set forced the token flow even when
--fjordwas spelled out. Explicit--fjordnow wins.FJ_SESSIONwas
bound tofj auth session --cookiethe same way, where it conflicted with
--clear; that binding is gone too. -
fj pr checkshandles a head with no reported checks. Forgejo returns
statuses: nullthere, which failed to decode. It now prints
no checks reported on <sha>and exits 0;--jsonstill emits a normal
combined-status object withstatuses: []. -
fj run view --logreads logs on Forgejo 16. Logs are resolved through
the run-jobs and job-log APIs, and displayed run numbers are mapped to API
run ids first, including for runs past the first page.FJ_TOKENprecedence
is preserved, so an env-token-only environment does not touch an unreadable
token store. A Forgejo 15.x host, which does not expose the
token-authenticated job log API, is now reported as such by version rather
than as a parse error. -
fj run view --logno longer downloads every task in the repository on
Forgejo 16. The native job-log path fetched the workflow task list first
and discarded it, and on 16 that endpoint ignores itsrunfilter: about
3 MB and 30 seconds on every log read against a busy repository. The task
list is now loaded only by the Loki fallback, which is the one path that
needs it, and that fallback also decodes theworkflow_runsenvelope 16
returns instead of aborting on an unexpected response shape. -
fj pr listandfj pr viewdecode Forgejo's system actors. Forgejo
uses negative sentinel user ids (-1for Ghost,-2forforgejo-actions),
and the sharedUsermodel readidas unsigned, so any repository with a
system actor as reviewer, assignee, poster, or author failed the whole decode
withinvalid value: integer -2, expected u64. The field is signed now,
which covers every actor position at once. -
A failed list decode names where it failed. List responses are decoded
throughserde_path_to_error, so the message carries the endpoint and the
JSON field path (for exampleGET /api/v1/repos/o/r/pulls?...and
field [0].id) instead of only the type error. -
Tag releases publish their assets, and the generated Homebrew formula
installs. Thev0.4.1release was published with zero assets, so
brew install fjserved 0.3.0 from 22 to 30 July: one build leg failed, and
re-running could not recover because artifact keys are scoped by run id, so
the legs that had already uploaded hit "artifact already exists" and the
publish job never ran. The assets were uploaded on 30 July by the recovery
dispatch these changes made possible, and the tap has served 0.4.1 since.
Artifacts are overwritten on a re-run now, and a release can be re-run by
workflow_dispatchwith ataginput, from a branch carrying a fix, without
moving the tag. The formula could not have installed even if publish had run:
it didcd fj-<version>-<target>, but Homebrew has already entered the
tarball's top-level directory and that directory keeps the tag'svprefix,
which the formula's version drops, sobrew installended in
Errno::ENOENT: chdir_path. Three failures that used to pass quietly now
stop the run: a missing matrix leg renderingsha256 "", an asset glob
matching nothing, and a missing CHANGELOG section for the tag (release
bodies were always empty, and are now taken from that section). A dispatched
tag also reaches the shell as data rather than as a substituted expression,
must exist in the repository's tags, and is checked out asrefs/tags/<tag>
with the resolved sha asserted in every job, so a branch sharing a
version-shaped name cannot be built and published as if it were the tag.
Downloads
-
Source code (ZIP)
3 downloads
-
Source code (TAR.GZ)
28 downloads
-
v0.4.1
StableSome checks failedci / check (push) Successful in 10m25sci / coverage (push) Successful in 1m41sci / live-e2e (push) Successful in 1m58srelease / build (catthehacker/ubuntu:act-22.04, linux-x86_64, docker, x86_64-unknown-linux-gnu) (push) Failing after 1m44srelease / build (darwin-aarch64, macos-15, aarch64-apple-darwin) (push) Successful in 3m49srelease / build (darwin-x86_64, macos-15, x86_64-apple-darwin) (push) Failing after 3m40srelease / publish (push) Has been skippedreleased this
2026-07-22 20:19:49 +00:00 | 87 commits to main since this releaseFixed
- Silent Fjord Account session refresh across every command. An expired
Fjord access token is now renewed transparently at the shared HTTP client: on
a 401 from a host signed with a Fjord bearer, fj refreshes via the stored
refresh token and retries the request once, sofj api,fj pr,fj issue,
fj repo, and the Actions log routes no longer fail with "sign in again" once
the short-lived token lapses. Previously onlyfj instancesandfj auth
refreshed. PAT hosts (whose tokens are not refreshable) and the case with no
usable refresh token surface the original 401 unchanged, and the refresh is
bounded to one attempt per request so a persistently-401 endpoint cannot loop.
Downloads
-
Source code (ZIP)
6 downloads
-
Source code (TAR.GZ)
13 downloads
- Silent Fjord Account session refresh across every command. An expired
-
v0.3.0
StableAll checks were successfulrelease / build (catthehacker/ubuntu:act-22.04, linux-x86_64, docker, x86_64-unknown-linux-gnu) (push) Successful in 2m35srelease / build (darwin-aarch64, macos-15, aarch64-apple-darwin) (push) Successful in 3m54srelease / build (darwin-x86_64, macos-15, x86_64-apple-darwin) (push) Successful in 3m53srelease / publish (push) Successful in 15sci / check (push) Successful in 10m18sci / coverage (push) Successful in 1m53sci / live-e2e (push) Successful in 1m53sreleased this
2026-06-29 22:45:47 +00:00 | 100 commits to main since this releaseDownloads
-
Source code (ZIP)
3 downloads
-
Source code (TAR.GZ)
5 downloads
-
Source code (ZIP)