112 releases 130 tags

RSS feed

• v0.18.1 f46fe001b8

  Compare

  Release v0.18.1 Stable

  release-bot released this 2026-06-28 21:54:28 +02:00 | 1410 commits to main since this release

  Fixed

  • scripts/repin.sh now tags every [repin] output line with its mode -- DRY-RUN: in dry-run, LIVE: in a real run (e.g. [repin] LIVE: detached bake commit: ..., [repin] DRY-RUN: PLAN). A dispatcher copy-pasting a bake-commit SHA from the output now sees the mode inline, so the dry-run bake (thrown away) can't be mistaken for the live one the rc tag actually points at. Closes a same-day n=2 mis-citation class that the per-re-pin verify discipline had been catching by hand.

  Downloads

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.18.0 bff22f2856

  Compare

  Release v0.18.0 Stable

  release-bot released this 2026-06-28 20:44:09 +02:00 | 1414 commits to main since this release

  Changed

  • The two reusable workflows are renamed to drop the _ prefix in favour of an explicit reusable- prefix: .forgejo/workflows/_release.yml -> reusable-release.yml and _manifest-check.yml -> reusable-manifest-check.yml. The _ prefix was an informal "internal" community signal; reusable- states the workflow_call shape outright and reads cleaner at the adoption surface (the consumer types the full reusable path in their uses: line). The consumer-wrapper names (release.yml, manifest-check.yml) are unchanged, as is all workflow runtime behavior -- this is a pure rename.

  Downloads

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.17.1 d461dedc81

  Compare

  Release v0.17.1 Stable

  release-bot released this 2026-06-28 18:57:25 +02:00 | 1419 commits to main since this release

  Fixed

  • The Layer 2 / Layer 3 cut-safeguard now finds the merged cut PR via Forgejo's direct commit->PR lookup (GET /repos/{owner}/{repo}/commits/{sha}/pull) instead of a pulls?state=closed&sort=updated&limit=5 list-and-filter. The old query paired an arbitrary 5-PR window with Forgejo's issue_id-descending sort=updated ordering, so a rolling cut PR created early but merged late could fall outside the window once more than a few PRs closed between cuts -- the safeguard then returned empty and the cut fell through to mode=update. (Anchor: the v0.17.0 cut, where rolling PR #227 sat at list position 11 of the limit=5 query and had to be recovered manually.) The direct lookup keys on the merged commit server-side and has no window to outgrow; a 404 (no PR for the commit, including the brief post-merge indexing-lag window) collapses to the existing empty-result contract that the caller's retry + protective fall-through already handle.

  Downloads

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.17.0 58acedf6fe

  Compare

  Release v0.17.0 Stable

  release-bot released this 2026-06-28 18:30:33 +02:00 | 1424 commits to main since this release

  Added

  • hooks: dogfood post_bump_hooks for own doc ref-pins (#209)
  • forgejo-api: emit api_call structured event (#204 part 1)

  Fixed

  • release-prep: relax origin requirement in dry-run (#216)
  • cut path: add [skip ci] to bake-reset commit to suppress CI noise (#202)

  Added

  Added examples/go-project and examples/node-project — complete drop-in consumer bootstraps (config + the two wrapper workflows + a CHANGELOG skeleton + version file) you can cp -r into a new repo to adopt the toolkit, plus an examples/README.md index. Post-Phase-2 shape (no toolkit_ref: input; @v0.16.0 pin).

  api_call structured event: forgejo_api_call now emits one JSON event per real API call (endpoint, method, status, ms) to stderr, giving Loki-ingestable observability over the toolkit's Forgejo interactions including latency and non-2xx failures. Emitted at the wrapper on every real call (not in dry-run); ms is the curl wall-clock in integer milliseconds. The emit is guarded so forgejo-api.sh keeps no hard dependency on the events substrate -- callers that sourced events.sh get the event, others degrade cleanly to no-emit. (Part 1 of #204; the workflow-level cut_complete.ms_total remains deferred to the next compose-script cut.)

  The toolkit now dogfoods its own post_bump_hooks on its own docs: a new hook (scripts/hooks/update-doc-version-refs.sh), wired in release-toolkit.yml, re-pins the adopter-facing example refs in README.md + docs/integration.md to the freshly-cut tag on every cut -- eliminating the manual doc-ref-pin drift class (#196 was the recurring manual fix; Shipwright #157 found the dogfooding gap). The hook preserves historical "feature-since" references (e.g. v0.12.0+) and pins only the @vX.Y.Z / Latest: / Replace example shapes. A new RELEASE_TOOLKIT_RELEASE_DATE env var is exported to all post_bump_hooks (the cut date, matching the CHANGELOG heading) so hooks can refresh dated examples. The post_bump_hooks docs now also document the staging convention (hooks must git add their own changes; release-prep commits only staged files).

  • hooks: dogfood post_bump_hooks for own doc ref-pins (#209)
  • forgejo-api: emit api_call structured event (#204 part 1)

  Changed

  docs: sweep adopter-facing ref pins (README + integration.md) to @v0.16.0 (#196).

  Fixed

  Corrected adopter-facing integration.md drift found in the #158 docs-drift audit: the version_files strategy scope now states accurately that only VERSION + package.json are handled (replacing the invented, mutually-contradictory "v0.3 scope"/"v0.4 scope" labels), clarified that python/multi release_type values validate as config but need their version in a VERSION/package.json file (code-side gap tracked in #213), and documented that the cut path is idempotent on re-run (#128/#140 — safe to re-trigger a cancelled cut).

  release-prep.sh --dry-run no longer requires a configured origin remote when none is present. Dry-run skips every remote write, and the sole use of origin is owner/repo inference that (in dry-run) feeds only dry-run-noop API calls plus the echoed owner=/repo= outputs -- so a fresh scratch repo with no remote can now preview a cut. The real git-history read (LAST_TAG via git describe) uses local tags, not the remote. A present-but-unparseable remote stays fatal even in dry-run (a genuine misconfiguration dry-run should surface), and production cuts still hard-require origin. Also fixes a latent silent-abort in the same path: an unparseable remote previously tripped set -e at the owner/repo assignment before the "could not derive owner/repo" diagnostic could print.

  • release-prep: relax origin requirement in dry-run (#216)
  • cut path: add [skip ci] to bake-reset commit to suppress CI noise (#202)

  Downloads

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.16.0 facc935f4e

  Compare

  Release v0.16.0 Stable

  release-bot released this 2026-06-28 13:06:07 +02:00 | 1441 commits to main since this release

  Removed

  • The toolkit_ref workflow_call input is removed from the reusables (_release.yml + _manifest-check.yml). The toolkit ref is now baked into the reusable at every pinnable point — cut tags at cut-prep, rc tags at re-pin via the new scripts/repin.sh (a detached bake commit the rc tag points at) — so uses:@<ref> is the single source of truth and the resolve-ref step reads the baked value unconditionally. This removes the second ref surface that could drift (toolkit_ref: vs uses:@) rather than merely enforcing their alignment.

  Downloads

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.15.0 84ffa63b5a

  Compare

  Release v0.15.0 Stable

  release-bot released this 2026-06-27 16:06:59 +02:00 | 1451 commits to main since this release

  Added

  • Structured JSON event logging substrate (scripts/lib/events.sh): event_emit KIND key=value... emits one JSON object per event to stderr for Loki ingest. The cut path is instrumented with cut_decided, manifest_skip/manifest_proceed, cut_complete, repin_check, and error events (release-toolkit#159).

  Downloads

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.14.0 ea070a8482

  Compare

  Release v0.14.0 Stable

  release-bot released this 2026-06-27 15:16:03 +02:00 | 1458 commits to main since this release

  Added

  • check-self-bootstrap: wrapper toolkit_ref alignment (closes #163)

  Fixed

  • build_bake: defense-in-depth ref-shape validation (closes #180)
  • config: reject path-traversal in version_files (closes #181)
  • fragments: FAIL-LOUD on unknown-kind via assert_no_unknown_kinds

  Downloads

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.13.1 df6b25da0a

  Compare

  Release v0.13.1 Stable

  release-bot released this 2026-06-27 13:44:53 +02:00 | 1466 commits to main since this release

  Fixed

  • check-self-bootstrap: normalize build-bake marker line before compare

  Downloads

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.13.0 5a2efa7533

  Compare

  Release v0.13.0 Stable

  release-bot released this 2026-06-27 12:00:03 +02:00 | 1471 commits to main since this release

  Added

  • Build-bake mechanism: release-prep.sh rewrites a marker-anchored ref: in _release.yml and _manifest-check.yml to the next-cut version, construction-enforcing the consistency between consumer uses: @<ref> and the toolkit checkout step (Phase 1 of release-toolkit#148).

  Downloads

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads
• v0.12.0 d64b2c68bf

  Compare

  Release v0.12.0 Stable

  release-bot released this 2026-06-27 10:53:17 +02:00 | 1479 commits to main since this release

  Added

  • auto-prune superseded -rc.N tags after cut (closes #153)

  Fixed

  • prune-rc-tags: self-pin exclusion (closes #167)

  Downloads

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