Record the completed 1.0.0 milestone in TODO.md #249
Reference in New Issue
Block a user
Delete Branch "todo-md-1.0.0-complete"
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?
Docs only —
TODO.mdand nothing else. The file still said the 1.0.0 milestone was "no longer complete" and described the deployability audit's findings as open problems; shipping that inside the tag would make the release contradict its own front page.# Statusnow states: 1.0.0 complete (55 closed, 0 open),next@687405962 commits ahead ofmainand a strict fast-forward, no git tags yet, and each audit gap rewritten as closed with its issue — #201, #200, #67, #202, #203, #204, #205, #206, #207.# Next Stepis now merging #111 and taggingv1.0.0, plus the non-blocking open items.# Future Stepshad three entries that landed during the milestone and read as false: manual redelivery ("no redelivery code exists anywhere in the tree"), signature verification, and password reset. Narrowed to what is actually left — Stripe HMAC, a web-based reset — rather than deleted.# Workflowand# Completed Stepsare untouched. Net -13 lines.Verification
make fmt: clean, no changes (this repo'sscript/fmtis Go-only, so the markdown was wrapped to the file's existing 72 columns by hand; no line exceeds it).Cache-defeated gate per #119, from this branch's clone:
docker build --no-cache-filter=lint --no-cache-filter=builder --progress=plain .— exit 0.golangci-lint(digest-pinned container):0 issues.at 48.36s, stageDONE 49.2smake testDONE 66.2s— 1081--- PASS:visible, 0--- FAIL:, 0--- SKIP:, 0(cached)make buildDONE 43.0sCACHEDvertices in thelintchain (#10-#17) or thebuilderchain (#18-#27). The 8 cached layers are the two digest-pinned base-image pulls and the sixstage-2runtime layers;COPY --from=builder /build/bin/webhookercached is expected here, since a docs-only change produces a byte-identical binary.Disclosure: BuildKit clipped the log at its 2 MiB limit inside the
make teststep ([output clipped, log limit 2MiB reached]), so 16 of 22 package result lines are visible in the gate log. The step exited 0 on its own, whichgo test ./...only does when every package passes.The lint stage emits the
gomodguarddeprecation warning already tracked as #248.