Release v0.6.0

stephen commented

2026-10-10 23:49:31 +00:00

Owner

Cuts v0.6.0. Six merges have landed since v0.5.0 with nothing in the changelog: the Fjord Account refresh and re-login fixes (#273, #274), the required-check glob fix (#275), and the spec-parity work (#278, #279, #281) that takes fj to every requirement of the fjord-client-spec.

Minor rather than patch because it adds command groups (admin, profile, org team, issue reaction|dependency|time, repo transfer, repo commit, repo contents, auth group, auth proxy) and changes output scripts can notice: fj status has a leading ID column, fj pr checks a REQUIRED column, fj variable list a new table and JSON shape, and fj label create|edit --color is now --label-color (the old spelling panicked at parse time, so nothing could have depended on it).

The spec-parity PRs were covered by unit and wiremock tests only, so before this I ran a main build against rasterhub.com: stephen/fj-cli-test plus a throwaway private org, all removed afterwards. Exercised and working: issue create --milestone, issue list --sort, issue reaction add|toggle|remove|list on an issue and a pull request, issue dependency add|remove|list in both directions including the duplicate, reverse-cycle and unknown-target refusals, issue time add|list|delete, pr review --line-comment (single, batched with --event, and the three local refusals), pr checks, status and status read, variable set|list|delete at repo and org scope, org create, every org team subcommand, label create|list --org with --exclusive, repo topics add|remove, and repo commit list with the signature column.

That turned up one bug, fixed in the first commit: fj issue time list printed its total on the last row of the table.

Not exercised live: fj admin (needs a site administrator and creates real users), fj profile edit|email|avatar, repo transfer, status unsubscribe|mute, the Commons and re-login paths (need a Fjord Account), the Gitea capability gates, and auth proxy. The "disabled on this repository" and "permission denied" wording for dependencies and tracked time is still unverified, since the test repo has both enabled and I own it.

Second commit is the mechanical release: version bump (Cargo.toml, Cargo.lock), README badge and install URLs, and the CHANGELOG [0.6.0] section. make release-preflight TAG=v0.6.0 passes runners and secrets and failed only on the version, which this fixes. Tag v0.6.0 after merge to trigger the release build.

Cuts v0.6.0. Six merges have landed since v0.5.0 with nothing in the changelog: the Fjord Account refresh and re-login fixes (#273, #274), the required-check glob fix (#275), and the spec-parity work (#278, #279, #281) that takes fj to every requirement of the fjord-client-spec. Minor rather than patch because it adds command groups (`admin`, `profile`, `org team`, `issue reaction|dependency|time`, `repo transfer`, `repo commit`, `repo contents`, `auth group`, `auth proxy`) and changes output scripts can notice: `fj status` has a leading `ID` column, `fj pr checks` a `REQUIRED` column, `fj variable list` a new table and JSON shape, and `fj label create|edit --color` is now `--label-color` (the old spelling panicked at parse time, so nothing could have depended on it). The spec-parity PRs were covered by unit and wiremock tests only, so before this I ran a main build against rasterhub.com: `stephen/fj-cli-test` plus a throwaway private org, all removed afterwards. Exercised and working: `issue create --milestone`, `issue list --sort`, `issue reaction add|toggle|remove|list` on an issue and a pull request, `issue dependency add|remove|list` in both directions including the duplicate, reverse-cycle and unknown-target refusals, `issue time add|list|delete`, `pr review --line-comment` (single, batched with `--event`, and the three local refusals), `pr checks`, `status` and `status read`, `variable set|list|delete` at repo and org scope, `org create`, every `org team` subcommand, `label create|list --org` with `--exclusive`, `repo topics add|remove`, and `repo commit list` with the signature column. That turned up one bug, fixed in the first commit: `fj issue time list` printed its total on the last row of the table. Not exercised live: `fj admin` (needs a site administrator and creates real users), `fj profile edit|email|avatar`, `repo transfer`, `status unsubscribe|mute`, the Commons and re-login paths (need a Fjord Account), the Gitea capability gates, and `auth proxy`. The "disabled on this repository" and "permission denied" wording for dependencies and tracked time is still unverified, since the test repo has both enabled and I own it. Second commit is the mechanical release: version bump (Cargo.toml, Cargo.lock), README badge and install URLs, and the CHANGELOG [0.6.0] section. `make release-preflight TAG=v0.6.0` passes runners and secrets and failed only on the version, which this fixes. Tag `v0.6.0` after merge to trigger the release build.

stephen added 2 commits

2026-10-10 23:49:31 +00:00

Put the tracked-time total on its own line 4104db488c

`fj issue time list` printed the table without a trailing newline, so
the "Showing N of M" note and the total landed on the last row. Found
running the new commands against a live forge before the release.

Release v0.6.0

ci / check (pull_request) Successful in 14m20s

Details

ci / coverage (pull_request) Successful in 2m30s

Details

ci / live-e2e (pull_request) Successful in 3m8s

Details

221e7d13d9