Skip to content

chore: release v0.13.1 - #834

Merged
REPPL merged 2 commits into
mainfrom
release/v0.13.1
Oct 5, 2026
Merged

REPPL merged 2 commits into
mainfrom
release/v0.13.1

Conversation

@REPPL

@REPPL REPPL commented Oct 5, 2026

Copy link
Copy Markdown
Collaborator

Release v0.13.1, cut autonomously on the product thinker's instruction of 2026-10-05 ("run all checks autonomously and cut a quick update release, also autonomously, e.g. v0.13.1"). When this merges, the tagging workflow reads the dated section and tags v0.13.1.

This is a patch release: fixes only, nothing to do when you update.

What ships, seven fixes in six changelog lines:

  • launch ship refuses a cut whose record folders differ from HEAD, instead of returning a plausible cut that silently leaves a record out (iss-2610050259118177).
  • abcd ahoy and session start name any abcd hook wired into the harness's user settings outside the plugin, and a status line whose binary fails the trust checks; abcd never edits that file to remove one (iss-2610050556323779).
  • The rename repair abcd prints reaches every worktree at any depth, and abcd ahoy names any it left unlinked (iss-2610050728100598).
  • dashboard start never signals a server that has already exited (iss-2610050859363813).
  • The status line is the one entry abcd writes in the harness's user settings, only on a yes, with the before and after shown, a backup kept, the write read back and restored on a mismatch, and only a trusted recorded binary wired (iss-2610050556383525).
  • The change guard's reading outside the tree is held to a budget instead of hashing for minutes (iss-2610040847166532, iss-2610050315146044).

launch ship derived v0.13.1 (impact fix) from the seven records that reached a terminal folder since v0.13.0. The release guard and the findings guard passed. No intent shipped, so RELEASE.md stays on 0.13.0.

The branch is two commits on main 4c38c11 (the merge of #831):

  • 71806f8, the roll. The 0.13.1 changelog section composed by the release-changelog-composer and ingested by launch ship, and the plugin archive pinned in the marketplace file. The ingest's deep smoke rendered every page and its parity against v0.13.0 shows 1 added, 10 changed, 0 removed.
  • 8ddfe08, the receipts, keyed to 71806f8. Both PROMOTE at shallow tier, which the receipt gate admits for a patch:
    • docs-currency-reviewer: every user-facing page the release touches and the changelog lines verified against the code and the built binary; one minor wording omission, deferred.
    • brief-surface crosscheck (Direction B, five surface checkers): the shipped surface matches the brief's tables; 25 findings in brief prose, each deferred to iss-2609091956001547.

abcd launch receipts passes on this branch, and make preflight passes on its tip.

Refs: iss-2610050259118177
Refs: iss-2610050556323779
Refs: iss-2610050728100598
Refs: iss-2610050859363813
Refs: iss-2610050556383525
Refs: iss-2610040847166532
Refs: iss-2610050315146044
Refs: iss-2609091956001547

Assisted-by: Claude:claude-opus-5-5

REPPL added 2 commits October 5, 2026 12:37
Assisted-by: Claude:claude-opus-5-5
Both gates PROMOTE at shallow tier for a patch release, keyed to the
content commit 71806f8: the docs-currency
review (one minor finding, deferred) and the brief-surface crosscheck
(25 brief-prose findings, each deferred to iss-2609091956001547).

Refs: iss-2609091956001547
Assisted-by: Claude:claude-opus-5-5
@REPPL
REPPL enabled auto-merge October 5, 2026 12:01
@REPPL
REPPL added this pull request to the merge queue Oct 5, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Oct 5, 2026
@REPPL
REPPL added this pull request to the merge queue Oct 5, 2026
Merged via the queue into main with commit 567bd54 Oct 5, 2026
22 of 23 checks passed
@REPPL
REPPL deleted the release/v0.13.1 branch October 5, 2026 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant