1.0.0 milestone #92
Reference in New Issue
Block a user
Delete Branch "next"
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?
Accumulates the 1.0.0 milestone. One squashed commit per closed issue, each landed on
nextonly after an independent adversarial review passed and bothmake checkandscript/cibuildwere observed green with the Docker cache defeated.Mergeable to
mainat any time, without notice — that is the invariantnextis maintained under. Contents grow as units land; this PR is not held back for a completeness criterion.Landed so far
.golangci.yml, all resulting findings fixed tree-wide. Two intended behavior changes: absentMFFilePath.Mtimehandled explicitly infreshen/list/export(mainpanicked on it), and an explicit--end-of-options marker before positionalgpgkey IDs. All twelve reworded user-visible error messages restored to byte-identical parity withmainand pinned by tests.script/fmtandscript/fmt-checkshare onescript/prettierentrypoint so they cannot drift; markdown formatting is gated in the Docker build via a newmdfmtstage;REPO_POLICIES.mdignored so local tooling cannot drift it from upstream. The|| truethat made the old prettier call unable to fail is gone.Verification note
The Gitea Actions runner has been down since 2026-08-09 (#93), so commits here carry no CI status. Every unit was instead gated by hand in a worker clone and independently re-verified by its reviewer, in both cases with the Docker layer cache defeated so the checks were observed executing rather than replayed — see #89 for why a plain
script/cibuildgreen is not currently trustworthy on its own.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.