112 releases 130 tags

RSS feed

• v0.46.1 b4ae44a543

  Compare

  v0.46.1 Stable

  release-bot released this 2026-08-26 09:49:30 +02:00 | 815 commits to main since this release

  Added

  None.

  Changed

  None.

  Fixed

  • dead-script documentation: freeze the 32-name namespace and classify every documented site by temporal provenance or citation shape (#852)

  • release: record the published v0.46.0 cut in the manifest

  • changelog: shorten manifest boundary fragment

  Removed

  None.

  Deprecated

  None.

  Upgrade

  None.

  Internal

  • manifest replay boundary: post-cut skips only when remote state records the cut head, so a current-run local manifest write cannot masquerade as prior-run bookkeeping (#862)

  • docker-build contract: fail release image jobs before Node-backed actions when runner capabilities are absent (#876)

    Publish and verify now log paths and versions for git, Docker CLI/daemon, jq, and Node, with a positive Docker control. No consumer action is required.

  • release recovery: expose pending cut version and prepare commit as a blocked decision, preventing rolling updates until an operator completes or reverts the cut (#882)

  Downloads

  • checksums.txt
    2 downloads · 2026-08-26 09:51:04 +02:00 · 81 B
  • rt-linux-amd64
    5 downloads · 2026-08-26 09:51:04 +02:00 · 9.4 MiB

  ---

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.46.0 7d248947f6

  Compare

  v0.46.0 Stable

  release-bot released this 2026-08-25 21:29:56 +02:00 | 824 commits to main since this release

  Added

  None.

  Changed

  • Release orchestration: move stateful cut bookkeeping behind a typed rt boundary (#862)

    Manifest transactions, self-workflow bake/re-pin, and cut-time push handoff now run through tested Go code while workflow-native wiring and fail-closed post-conditions remain in YAML.

  Fixed

  • release: satisfy post-cut lint contracts

  Removed

  None.

  Deprecated

  None.

  Upgrade

  None.

  Downloads

  • checksums.txt
    3 downloads · 2026-08-25 21:31:31 +02:00 · 81 B
  • rt-linux-amd64
    5 downloads · 2026-08-25 21:31:31 +02:00 · 9.4 MiB

  ---

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.45.1 de927aad62

  Compare

  v0.45.1 Stable

  release-bot released this 2026-08-25 18:41:16 +02:00 | 830 commits to main since this release

  Added

  None.

  Changed

  None.

  Fixed

  None.

  Removed

  None.

  Deprecated

  None.

  Upgrade

  None.

  Internal

  • CI gates now consume measured standard runner images — missing bats, shellcheck, jq, or Graphviz fails loud instead of triggering runtime package installation (#863)

  • Release cuts now publish the digest-pinned action from the measured Docker-capable runner and hand the tagged action artifact to verification (#872)

  Downloads

  • checksums.txt
    3 downloads · 2026-08-25 18:43:01 +02:00 · 81 B
  • rt-linux-amd64
    5 downloads · 2026-08-25 18:43:01 +02:00 · 9.4 MiB

  ---

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.45.0 74b059ff65

  Compare

  v0.45.0 Stable

  release-bot released this 2026-08-25 17:37:38 +02:00 | 835 commits to main since this release

  Added

  None.

  Changed

  • contracts: enforce C6 section-header grammar against shipped changelogs (#799)

    The Go contract test now checks level-3 section headers with an accept/reject control and refuses to grade a missing or empty section corpus.

  Fixed

  None.

  Removed

  None.

  Deprecated

  None.

  Upgrade

  None.

  Downloads

  • checksums.txt
    2 downloads · 2026-08-25 17:39:08 +02:00 · 81 B
  • rt-linux-amd64
    4 downloads · 2026-08-25 17:39:08 +02:00 · 9.4 MiB

  ---

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.44.2 e9b51bea30

  Compare

  v0.44.2 Stable

  release-bot released this 2026-08-25 17:12:44 +02:00 | 839 commits to main since this release

  Added

  None.

  Changed

  None.

  Fixed

  • rt manifest-pr skips assigning the manifest PR to a configured bot identity, retaining release-bot as the default (#722)

  Removed

  None.

  Deprecated

  None.

  Upgrade

  None.

  Downloads

  • checksums.txt
    2 downloads · 2026-08-25 17:14:16 +02:00 · 81 B
  • rt-linux-amd64
    5 downloads · 2026-08-25 17:14:16 +02:00 · 9.4 MiB

  ---

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.44.1 55c35c72fa

  Compare

  v0.44.1 Stable

  release-bot released this 2026-08-25 16:58:42 +02:00 | 843 commits to main since this release

  Added

  None.

  Changed

  None.

  Fixed

  • changelog-body-check: reject duplicate version sections across the full changelog (#791)

    The gate reports the competing version lines; repeated kind headers remain scoped to the newest release section.

  • rt repin recovers cleanly from a failed tag push by publishing the detached bake directly and naming remote verification before retry (#796)

  Removed

  None.

  Deprecated

  None.

  Upgrade

  None.

  Downloads

  • checksums.txt
    2 downloads · 2026-08-25 17:00:19 +02:00 · 81 B
  • rt-linux-amd64
    4 downloads · 2026-08-25 17:00:19 +02:00 · 9.4 MiB

  ---

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.44.0 347028a2e5

  Compare

  v0.44.0 Stable

  release-bot released this 2026-08-25 12:02:46 +02:00 | 849 commits to main since this release

  Added

  None.

  Changed

  Duplicate-version refusal: the ## [vX.Y.Z] already present error now names what it did NOT check.

  It detects a duplicate heading and nothing more. The tag may exist. The release may have published. The section's body may be incomplete. None of that is verified.

  Its "did not tag it" clause names a likely cause, not a measured one — a hand-edited CHANGELOG reaches the same state.

  Applied at both emit sites together (#833, #659).

  Fixed

  Release prep: a second prep run for a version already in the changelog now merges into that section instead of refusing the cut.

  The transition transforms ## [Unreleased] into a version heading. It never scanned for an existing one, so a second run emitted a duplicate.

  Refusing would strand real content. The second run's Unreleased holds everything accrued since the first. Merging keeps both sets, and None. placeholders drop out.

  The existing heading keeps its date, so a tagged section is never restamped (release-toolkit#665).

  Fixed: the four PR-CI gates now build rt from the commit under test, not from main.

  Each gate checks the toolkit out a second time. That checkout resolves to main under the #456 floating-pin override. So a PR that changed a gate was graded by main's copy of it — the gate under test was never the gate that ran.

  The build arm now sources from the consumer checkout when it carries cmd/rt. That is the PR itself when the toolkit runs its own CI.

  The adopter path is unchanged. An adopter has no cmd/rt in its workspace, so it still fetches a published asset and needs no Go toolchain.

  Code comments: internal/fragments/fragments_test.go no longer names fragments.sh as the byte-authority for the changelog-kind order.

  That script went with the bash PR-CI gates (#607). Kinds is the authority now; the port's origin stays in the past tense.

  Found by re-deriving #734's scope during its AC sweep. It fixed five scripts. fragments.sh was not among them — the floor its own AC warned about.

  register-check now covers the complete built-in chamber vocabulary.

  Docs: thirteen sites named a retired script as the present-tense actor for behaviour that still happens. rt repin and rt check-self-bootstrap do the work now, including the glossary's definition of "re-pin" and two table cells citing line numbers inside a file that no longer exists.

  The behaviour was never wrong; only the actor was. That is why a tense sweep misses them — a reader asking "is this still true?" gets yes.

  Corrected five code comments that justified best-effort error handling by claiming the cut had already published.

  The code they annotate never reads publish_mode. The claim was false under the old draft default and true again under immediate, while the reasoning it supports never depended on either. The justification is now that the release object exists, which holds under both.

  Contracts + workflow comments: four contract documents named a deleted scripts/lib/*.sh file as their byte-authority. The Go packages are the authority; the bash origin stays in the past tense.

  C4, C6 and C7 now point at internal/fragments, internal/changelog and internal/forgejo. fragment-format.md also claimed the contract validates "both substrates" — there is one.

  reusable-release.yml had two: a pointer to a deleted file, and a sentence asserting other scripts/lib sources still exist. None do.

  fetch-rt.sh's HTML guard now removes the page it rejected before exiting.

  Previously the page stayed on disk. That was harmless on the default path, where the work dir is a throwaway mktemp -d. With RT_INSTALL_DIR set it was not. That directory is the adopter's persistent #606 cache, so the rejected page sat there under the release asset's own name.

  The artefact is removed, never the directory. A blanket cleanup would delete the cache #606 exists to keep.

  rt repin and rt consumer-wrappers now discover .forgejo/workflows/*.yaml adopter wrappers, not only *.yml.

  This forge executes both extensions. A .yaml adopter was invisible to Discover, so the re-pin rewrite silently did nothing rather than failing.

  The .yml-only filter was inherited from the bash oracle (scripts/lib/wrappers.sh) and faithfully ported at #705. The port was correct; the oracle was wrong.

  Docs: docs/events-logging.md had a Go heading over a bash body. The call signature, the jq escaping, the event_emit return contract and the declare -F guard all described the retired shell layer.

  The deeper defect was the opening sentence. It said the toolkit emits events during the cut path. It does not: rt check-self-bootstrap is the only command that emits anything, and the taxonomy table listed seven kinds as "currently emitted" when one is.

  That retirement was deliberate and reasoned, recorded in internal/decide. The guide now says so instead of describing behaviour a reader will not observe.

  Updated live Forgejo integration and architecture documentation after the shell client retirement; historical provenance remains, and deleted-file line coordinates are no longer presented as current anchors.

  • register: genericize newly matched reviewer credits

  Removed

  None.

  Deprecated

  None.

  Upgrade

  None.

  Internal

  Added positive and negative Go tests for register-check allow-list glob semantics, including wildcard and recursive directory behavior.

  Removed the 55 changelog and config fixtures left orphaned when their equivalence suites were retired.

  Strengthened the workflow bake-list regression guard to count each reusable on both runtime staging loops, preventing prose occurrences from masking a missing loop entry.

  Downloads

  • checksums.txt
    2 downloads · 2026-08-25 12:04:22 +02:00 · 81 B
  • rt-linux-amd64
    3 downloads · 2026-08-25 12:04:22 +02:00 · 9.4 MiB

  ---

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.43.0 e6b57ce057

  Compare

  v0.43.0 Stable

  release-bot released this 2026-08-21 21:20:56 +02:00 | 876 commits to main since this release

  Added

  • release: publish the rt image and verify adopters can pull it
  • rt: bake-digest — the cut-time rewrite #794's coupling depends on
  • action: docker action, digest-pinned — the verified half of #794
  • prep: mirror the density verdict into the rolling PR description

  Changed

  Docs: branch-strategy.md and test-strategy.md no longer describe the retired two-line model in the present tense.

  Both already carried supersession notes. Both still opened with prose asserting the v2.x/v2/next plan as current or targeted. A header saying "superseded" does not reach a reader who starts at the first paragraph.

  branch-strategy.md now says which part survives: the single-thread cut model in §1 is still how the toolkit cuts. The multi-thread target never shipped.

  scripts/repin.sh and scripts/lib/forgejo-api.sh are retired. rt repin replaces them.

  The re-pin is now a Go verb. It validates the rc tag, builds the detached bake, then mints and pushes it. It rewrites each wrapper's pin, commits in a throwaway worktree, and opens the PR.

  Run rt repin <vX.Y.Z-rc.N>. AGENTS.md §2.5 documents it.

  ⚠️ --dry-run differs from the retired REPIN_DRY_RUN=1. The bash built the detached bake so it could be inspected. The Go reports the plan only.

  • contracts: fold validate-grammars.sh into the Go test suite (#777)

    The C4 and C6 grammars are now validated by go test, on every PR. The shell script was invoked by no workflow, so these grammars had never run under CI.

    TestC4AgainstHistoricalCorpus checks every fragment filename in git history. TestC6AgainstShippedChangelog checks every heading in the shipped changelog. Each carries accept/reject controls so a grammar that accepts everything cannot produce a clean scan.

    An empty corpus fails rather than skipping. A skip prints ok and exits 0, which a gate cannot distinguish from a pass.

  The architecture docs now say how much bash remains, not how many .sh files.

  One .sh file is left — fetch-rt.sh, 171 lines. A further 1315 lines live in workflow run: blocks across 12 files. reusable-release.yml alone carries 798.

  That bash is deliberately out of the retirement's scope. The port's subject was the script layer, not every shell command in CI. The judgement was never written down, so the docs read as if the bash were gone.

  ⚠️ "No bash files" and "no bash" are different claims. Only the first is true.

  rt: rt --version now carries build provenance. A source build reports dev (<sha>), or dev (<sha>, dirty) on a modified tree, read from Go build info. A goreleaser build still reports its tag unchanged. Previously any untagged build printed the bare string dev, so a stale binary and a broken gate were indistinguishable in CI output (closes part of #792).

  The release-toolkit action is now a docker action pinned by image digest.

  There are no inputs. version: and token: are gone. The action ref alone determines the binary, so the two can no longer disagree.

  A workflow still passing them keeps working. Actions ignores an undeclared input, so nothing breaks — the binary comes from the action ref instead.

  Run the action after actions/checkout. It installs under $GITHUB_WORKSPACE, which a later checkout wipes.

  Release cuts publish automatically again. publish_mode now defaults to immediate, reverting the #332 change that made draft the default.

  draft still works and is unchanged. Set it via RT_PUBLISH_MODE, the publish_mode: field in release-toolkit.yml, or the workflow input. The cut then creates the release unpublished, for a manual Publish click.

  Fixed

  Docs: four PR-CI gates carried a comment asserting that the @main bootstrap path builds the commit under test. It builds main.

  The gates check the toolkit out a second time, and that checkout resolves to main. So a PR that changes a gate is graded by main's copy of that gate (#728). Three of the four stated the opposite inside an otherwise-correct explanation of the cache decision; the fourth said it in different words.

  That explanation's real job — why version-tag refs are the only cacheable ones — was right and is unchanged. The false clause sat beside it as an aside, so a reader auditing the caching had no reason to check it.

  Comments only. No gate behaviour changes. The mechanism itself is #728 half B.

  The workflow parse check now covers every workflow file.

  It globbed reusable-*.yml, so it graded 5 of 16. A syntax error in any of the other 11 went unseen.

  That failure is silent by nature. A workflow which does not parse produces no run at all: no red, no status, nothing to investigate.

  Docs: secrets: inherit is required, not recommended. Omitting it is associated with a release PR that receives no CI at all.

  Measured across all four known adopters. The one repo that omits the line is the one whose rolling release PR has never received a single pull_request run.

  The PR still opens and still reads mergeable. Nothing goes red, because nothing runs, and a PR with zero checks looks like one whose checks passed.

  ⚠️ The guide said "omitting inherit degrades benignly" and labelled the line # recommended. One adopter followed that. Why it happens is not yet settled.

  Docs: arc42/07 §7.5 and arc42/05 no longer describe the Codeberg mirror as a live surface. #803 deleted both mirror workflows and left the deployment view asserting them in the present tense.

  §7.5 is kept as a dated what-was record rather than removed — the mirror was one of the two deployment-side concerns §7 exists to name. Its Substrate-verified (2026-07-08) anchor is untouched: that line is a true past-tense record and stays.

  arc42/05 listed reusable-mirror-to-codeberg.yml as a current adopter-visible building block. The live listing now matches the five reusables on disk, with the retired sixth named explicitly so a reader can tell retired from undocumented.

  Docs: README.md and docs/integration.md no longer open by calling release-toolkit "Codeberg-primary". #793 retired the mirror; both documents went on asserting Codeberg as the project's source, release and tag surface.

  The replacement states what is measurable: release-toolkit is developed on a self-hosted, LAN-only Forgejo and has no public mirror. Codeberg does not accept code that is largely LLM-generated, and a public mirror waits until there is adoption to serve.

  Codeberg as a platform for your repository is unaffected, and the docs now say so explicitly rather than leaving a reader to infer it. The 2026-07-05 companion demo is stated as a dated demonstration rather than a live guarantee — no CI arm here exercises a Codeberg target.

  docs/integration.md also linked reusable-mirror-to-codeberg.yml, a file deleted in #803.

  The workflow parse check now asserts its own coverage, not just its verdict. It previously looped a glob and printed OK. Grading 16 files and grading 5 produced byte-identical output, so narrowing the glob reddened nothing.

  It now counts what it parsed and compares that against an independent enumeration. Both sides cover *.yaml as well as *.yml, because this forge loads both — an unparseable .yaml workflow was invisible to the check.

  • changelog: split two over-long sentences in the #728 fragment
  • changelog: SectionContent distinguishes a MISSING section from an empty one
  • tests: restore main's parse arm verbatim — my own fix reverted more of #812

  Removed

  The Codeberg mirror is retired. mirror-on-cut.yml and reusable-mirror-to-codeberg.yml are deleted.

  Codeberg rejects code that is largely LLM-generated. No mirror replaces it. A public mirror waits until there is adoption to serve.

  Adopters who forked either workflow keep working — nothing here reaches a fork.

  ⚠️ The shape those files used is still right for any future mirror: a separate release: published workflow, never an in-graph mirror: job. An in-graph job trips Forgejo Actions' schema validator.

  The mirror had fired on every cut since 2026-08-17. Ten runs, all reporting success, against a repository that does not exist.

  Deprecated

  None.

  Upgrade

  None.

  Downloads

  • checksums.txt
    2 downloads · 2026-08-21 21:22:35 +02:00 · 81 B
  • rt-linux-amd64
    4 downloads · 2026-08-21 21:22:35 +02:00 · 9.4 MiB

  ---

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.42.0 baa31abad3

  Compare

  v0.42.0 Stable

  release-bot released this 2026-08-20 10:42:01 +02:00 | 925 commits to main since this release

  Added

  rt repin re-pins consumer wrappers to a release-candidate tag.

  It refuses a dirty tree or an existing tag. It builds the detached bake commit at the requested base, then mints and pushes the rc tag on it. It rewrites each wrapper's uses:@<ref>, commits in a throwaway worktree, pushes and opens the PR.

  The rewrite is ported verbatim from repin.sh. A third-party uses: line, or a fork under another owner, is left alone.

  --dry-run reports what would change and writes nothing.

  • ci: ask the Forgejo engine whether it can parse the workflows (#769)

  Changed

  Port scripts/setup-bump-labels.sh to rt setup-bump-labels --owner <owner> --repo <repo>. Creates bump/{patch,minor,major} as an exclusive label group on a Forgejo repo; idempotent: already-correct labels are skipped, labels missing exclusive=true are updated. Adds ListLabels, CreateLabel, and UpdateLabel to the Forgejo client. Deletes the shell script.

  • Document the terminal bash-retirement state: scripts/fetch-rt.sh remains as the single bootstrap fetch-and-verify script because it obtains rt itself.
  • ADR-0009 and the architecture docs now name the delivery-mechanism change that would retire the residual. The stale ADR-0007 VERSIONING link is also fixed.

  Fixed

  decide: rt decide's #417 orphan walk now discriminates release plumbing from adopter work by file scope, not commit type. A bump-worthy commit touching only the changelog, the manifest or a declared version_file no longer breaks the walk. The buried-prepare skip stays reachable, so a legitimate cut is not refused. #650 fixed this in release-decide.sh, which was retired before the fix reached Go — it had been shipping on no surface at all (closes #701).

  Arm 30 in tests/workflows.bats now parses the workflow instead of scanning its raw lines.

  It previously skipped every comment line. That let release-toolkit#757 land the ${{ }} form inside a run: block comment, where the expression engine reads it before bash sees the #, and every cut was blocked.

  Skipping nothing over-corrects: a # at YAML level, or inline on a plain scalar, is stripped by the parser and is safe. The arm now walks the string scalars that survive yaml.safe_load, which is the text the engine sees.

  • Add an erratum to the v0.37.1 changelog entry whose file-scope orphan discriminator shipped only in scripts/release-decide.sh, not rt decide.

  • gates: exemptions carry an occurrence quota, not a boolean (#772)

  • changelog.d: 772 fragment described the rule the previous commit removed

  • gates: backticks cannot exempt a citation — narrow to a measured allowlist (#772)

  • setup-bump-labels: S1016 type conversions + ADR-0009 ancillary bucket

  • rt: repin never writes the operator's checkout, on any path

  • rt: repin mints the tag it demands be absent, and stops writing on --dry-run

  • tests: arm 30 parses the workflow rather than scanning raw lines

  Removed

  None.

  Deprecated

  None.

  Upgrade

  None.

  Internal

  The #690 membership fallback's bounded window now has a negative arm.

  findPRContainingSHA asserts in its own comment that a prepare outside the window resolves to not-found and Layer 2 fails. Nothing exercised that: every membership arm placed the containing PR inside the window, so the bound could not fail where those arms ran.

  A widening window would turn a stale prepare into a spurious cut — worse than the false refusal #690 fixed, because a refusal gets investigated.

  AGENTS.md now records that rt repin is not yet the canonical re-pin path.

  scripts/repin.sh still implements the operation and the docs correctly name it canonical. The verb ships but nothing invokes it, and its forge path has never run against a real forge.

  The note is removed when #705 part B retires the script.

  • docs: repoint four Go comments at the real cli-surface contract path, and make the citation checkable (#772)

    Four comments cited contracts/cli-surface.md, which resolves from nowhere. The file is at docs/architecture/contracts/cli-surface.md, and one comment already said so.

    TestCitedDocPathsResolve now checks every repo-relative Markdown path cited in a Go comment. Two sites quote an unresolvable path as evidence; both are named in an explicit allowlist.

  Downloads

  • checksums.txt
    138 downloads · 2026-08-20 10:43:47 +02:00 · 81 B
  • rt-linux-amd64
    44 downloads · 2026-08-20 10:43:47 +02:00 · 9.3 MiB

  ---

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.41.0 a47f4d47db

  Compare

  v0.41.0 Stable

  release-bot released this 2026-08-20 02:52:33 +02:00 | 950 commits to main since this release

  Added

  rt consumer-wrappers now owns consumer-workflow discovery, and the release workflow uses it instead of sourcing the Bash helper.

  Changed

  rt manifest-postcondition now resolves the manifest-PR surface itself when --pr-state is unset. reusable-release.yml no longer sources scripts/lib/forgejo-api.sh; the flag is still honoured.

  Resolution fails closed. A lookup that cannot complete yields ungraded (exit 2), never absent (exit 1).

  This also closes a pagination hole. The old query read only the first 50 open PRs, so a busy repo could report absent while a manifest PR existed.

  rt binary-size-check replaces scripts/binary-size-check.sh (rt#720, bash retirement arc). Exit codes are tri-state: 0 pass, 1 step change exceeded, 2 could not grade. Flags --max-growth-pct, --baseline-bytes, and --attribute-ref are identical to the shell script. On a red, the merge-base attribution block is included. go-ci.yml calls rt binary-size-check directly; the shell script is deleted.

  rt check-self-bootstrap now owns pin-drift detection. The Bash script and its two private libraries are retired, and forgejo-api.sh no longer emits api_call events.

  rt prep now re-pins adopter-facing doc refs as a built-in step (rt#720, bash retirement arc). scripts/hooks/update-doc-version-refs.sh is deleted; the same rewrite logic runs as §8d UpdateDocVersionRefs inside rt prep — no consumer config change required. release-toolkit.yml no longer lists the hook in post_bump_hooks. The post_bump_hooks mechanism itself is retained for adopters.

  Fixed

  • release: an expression spelled out in a run-block comment made reusable-release.yml unusable (#762)

  Removed

  None.

  Deprecated

  None.

  Upgrade

  None.

  Internal

  • build-bake: retire the bash marker-rewrite library.

    No action required. rt build-bake now owns the post-cut marker reset and the re-pin detached bake path, preserving the existing tree semantics while removing the duplicated sed implementation.

  • code comments: stop naming deleted bash scripts as the current authority (#734)

    Fifteen Go files carried comments asserting that a removed script is the byte-authority or behaviour-of-record. Provenance statements are kept in the past tense; role assignments now name the Go package as the authority. No behaviour change.

  • forgejo-api.sh: correct the layer-2 comment — the documented fallback is the only path (#737)

    config.sh was removed in #712, so config_get_default_branch is never defined and the inline yq read is all that runs. The comment named the dead branch as the common case. Code unchanged.

  • rt: derive the subcommand phase census instead of hand-writing it twice.

    No action required. The comment above var subcommands named five Phase 6, six Phase 6b and three Phase 7 verbs. The slice holds 5 + 8 + 4 + 1, and Phase 8 was missing.

    TestAllSubcommandsPresent now derives the breakdown, so its failure message names the phase that moved. The comment carries no counts. The total stays hand-written: it is the gate, and a new verb should cost a deliberate bump.

  Prune the orphaned internal/bake/testdata fixture corpus left behind when the differential bake oracle was retired.

  Delete scripts/dev-tools/migrate-releases-to-codeberg.sh (0 callers, one-time historical mirror script) and scripts/lib/wrappers.sh (superseded by internal/wrappers/discover.go; scripts/repin.sh repointed to rt consumer-wrappers). Delete tests/wrappers.bats alongside wrappers.sh; equivalent coverage lives in internal/wrappers/discover_test.go.

  Downloads

  • checksums.txt
    6 downloads · 2026-08-20 02:54:12 +02:00 · 81 B
  • rt-linux-amd64
    7 downloads · 2026-08-20 02:54:12 +02:00 · 9.3 MiB

  ---

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads