frankenbit/release-toolkit
frankenbit/release-toolkit
15
1
Fork 0
Code Issues 11 Pull requests Projects Releases 106 Packages 1 Wiki Activity Actions
106 releases 124 tags
  • v1.0.0-alpha.0 271cc0150c

    v1.0.0-alpha.0 — the abandoned Go version line, retained for build-ref-check
    Some checks failed
    go-ci / lint + build + test (push) Failing after 5s
    Details
    goreleaser / build + publish rt asset (push) Successful in 1m20s
    Details
    Pre-release

    shipwright released this 2026-07-25 00:13:54 +02:00 | 1019 commits to main since this release

    This is a real cut from an abandoned version line, not a test artefact — and it is retained on purpose.

    What it was

    The toolkit's release logic was originally bash. The port to Go was planned as a parallel version line: ADR-0009 (go-substrate-for-v1) scheduled v1.0.0-alpha.N for dogfood and iteration, with phase 0a's exit criterion written as "asset publish works to v1.0.0-alpha.0 tag". ADR-0008 records the earlier v2.0.0 framing and its retarget — "retargets the port to v1.0.0 and collapses the two-line branch model".

    So v1.0.0-alpha.0 is the Go line's first cut, made while the bash trunk continued to release v0.x underneath it. The tags show the two lines running side by side and never crossing:

    v0.33.0          2026-07-23      bash trunk
v1.0.0-alpha.0   2026-07-25      the Go line's only cut
v0.34.0          2026-07-29      bash trunk, uninterrupted

    The two-line model was then dropped: Go development moved to trunk and v0.x numbering resumed. No v1.0.0-alpha.1 was ever cut. This tag is the whole of that line.

    Why it stays

    🔴 Deleting it would remove a shipped gate's only real-world failing case. It was published with BUILD_BAKED_TOOLKIT_REF: 'main' — a tree tagged without being baked for its own tag — and cmd/rt/build_ref_check_test.go points at it deliberately:

    "not a fixture: v1.0.0-alpha.0 is published history"

    build-ref-check has no other instance of that defect and one cannot be manufactured: the tree, the tag and the mis-baked ref have to be real. Four test files and two workflows reference it, and mirror-release.yml's since_tag default is this tag.

    What it is not

    Not a current version, not a version line anyone should pin, and not evidence of a 1.0 release. The project is pre-1.0 and its live line is v0.x. A reader browsing releases should treat this as history with a purpose, not as a version ahead of the others.

    Downloads