Release v0.5.0 #271
Loading…
Reference in a new issue
No description provided.
Delete branch "release-v0.5.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Cuts v0.5.0. The main user-facing reason is the Fjord Account default: every released
fjstill signs in againstforgejo-site.pages.dev, which sits behind Cloudflare Access, sofj auth login --fjordcompletes in the browser and then fails on the token exchange with an Access HTML page.mainhas defaulted tohttps://fjord.shsince #251.Minor rather than patch because [Unreleased] carries new commands (
stack shiprestack,run logs, Commons infj instances, host-scopedFJ_TOKEN_<HOST>, fast-forward-only merges) and one behavior change scripts can notice:pr mergewithout--stylenow follows the repo'sdefault_merge_styleinstead of assumingmerge.Mechanical release commit: version bump (Cargo.toml, Cargo.lock), README badge + install URLs, and a CHANGELOG [0.5.0] section. Also adds the two entries #266 did not cover: fast-forward-only merge style (#267) and the Forgejo 16 task-list fetch on log reads (#270). Tag
v0.5.0after merge to trigger the release build.