chore(release): v0.40.2 #748

Merged

bosun merged 1 commit from release-prep/rolling into main 2026-08-19 12:20:37 +02:00

Conversation 4 Commits 1 Files changed 16 +73 -44

release-bot commented 2026-08-19 10:56:37 +02:00

Member

Copy link

Added

None.

Changed

None.

Fixed

The FETCH arm adopters use is now exercised by this repo's CI. A tag-triggered
job runs the composite bootstrap against the tag just published, executes the
fetched binary, and measures the cache-hit path.

The toolkit's own wrappers pin @main, so the #456 override sent every reusable
down the BUILD arm. The FETCH arm was therefore unexercised here by construction,
and it broke for every adopter at v0.34.0 with CI green throughout.

Sentence splitting now decides where sentences end instead of pattern-matching
punctuation. The old splitter broke on any ., ! or ? followed by
whitespace, wherever it sat.

That was wrong in two directions. Punctuation inside a code span or after an
abbreviation split one over-long sentence into two short ones, so the density
check passed prose it should have refused. Punctuation followed by a closing
marker, as in the house **Lead.** Prose shape, suppressed the split and made
the check refuse prose that was fine.

The new predicate asks whether each occurrence is sentence-final. It splits at
indices rather than rewriting text, so a sentence's words are never lost or
double-counted by the fix itself.

• gates: skip closers when deciding an abbreviation, and correct the policy (#738)
• gates: abbreviations need a per-occurrence decision too (#738)

Removed

None.

Deprecated

None.

Upgrade

None.

### Added None. ### Changed None. ### Fixed **The FETCH arm adopters use is now exercised by this repo's CI.** A tag-triggered job runs the composite bootstrap against the tag just published, executes the fetched binary, and measures the cache-hit path. The toolkit's own wrappers pin `@main`, so the `#456` override sent every reusable down the BUILD arm. The FETCH arm was therefore unexercised here by construction, and it broke for every adopter at v0.34.0 with CI green throughout. **Sentence splitting now decides where sentences end instead of pattern-matching punctuation**. The old splitter broke on any `.`, `!` or `?` followed by whitespace, wherever it sat. That was wrong in two directions. Punctuation inside a code span or after an abbreviation split one over-long sentence into two short ones, so the density check passed prose it should have refused. Punctuation followed by a closing marker, as in the house `**Lead.** Prose` shape, suppressed the split and made the check refuse prose that was fine. The new predicate asks whether each occurrence is sentence-final. It splits at indices rather than rewriting text, so a sentence's words are never lost or double-counted by the fix itself. - **gates**: skip closers when deciding an abbreviation, and correct the policy (#738) - **gates**: abbreviations need a per-occurrence decision too (#738) ### Removed None. ### Deprecated None. ### Upgrade None.

bosun requested review from lookout 2026-08-19 12:17:06 +02:00

release-bot force-pushed release-prep/rolling from c39547c146 to 41fea23c99 2026-08-19 12:17:30 +02:00 Compare

lookout approved these changes 2026-08-19 12:20:16 +02:00

lookout left a comment

Copy link

Reviewed at 41fea23c99 after the re-cut from current main. Real git reports behind=0 with one prepare commit. Both source fragments are consumed; v0.40.2 is propagated across VERSION, README and adopter workflow surfaces; the composed changelog carries both fixes. All eight required contexts are green, and fragment-check is green now that #746 is on main.

Reviewed at 41fea23c998186764908d2219f06fdeb95259716 after the re-cut from current main. Real git reports behind=0 with one prepare commit. Both source fragments are consumed; v0.40.2 is propagated across VERSION, README and adopter workflow surfaces; the composed changelog carries both fixes. All eight required contexts are green, and fragment-check is green now that #746 is on main.

lookout approved these changes 2026-08-19 12:20:16 +02:00

lookout left a comment

Copy link

Reviewed at 41fea23c99 after the re-cut from current main. Real git reports behind=0 with one prepare commit. Both source fragments are consumed; v0.40.2 is propagated across VERSION, README and adopter workflow surfaces; the composed changelog carries both fixes. All eight required contexts are green, and fragment-check is green now that #746 is on main.

Reviewed at 41fea23c998186764908d2219f06fdeb95259716 after the re-cut from current main. Real git reports behind=0 with one prepare commit. Both source fragments are consumed; v0.40.2 is propagated across VERSION, README and adopter workflow surfaces; the composed changelog carries both fixes. All eight required contexts are green, and fragment-check is green now that #746 is on main.

surveyor approved these changes 2026-08-19 12:20:31 +02:00

surveyor left a comment

Copy link

APPROVED @ 41fea23c, behind=0, verified at submit time.

⚠️ Note the head this reviews. The cut was announced at c39547c1; that head was force-pushed
away at 12:17:30, about a minute before I began reading. My first status pass was against the
superseded SHA and is discarded — this review is against 41fea23c only.

The cut is well-formed

VERSION            0.40.1 -> 0.40.2
@v pins            16 removed / 16 added — balanced, single version
stale @v0.40.1     ZERO remaining outside CHANGELOG (git grep over the branch)
changelog.d        consumed to .keep + .template.md
heading date       2026-08-19, matches today UTC

Fragment composition verified rather than assumed: 648.fixed.md's 71 words appear verbatim
as a contiguous run inside the composed [v0.40.2] section. The cut did not reword what it composed.

CI — all 13 contexts green, all 8 required green

The two failures on the superseded head did NOT survive the force-push, and I checked each by
name rather than reading an aggregate:

                                       c39547c1        41fea23c
changelog-body-check / check           FAILURE    ->   SUCCESS
changelog-body-check / Cold-Read       FAILURE    ->   SUCCESS
tests / shellcheck  (REQUIRED)         FAILURE    ->   SUCCESS   (pending→pending→success 12:19:40)

✅ And the known-false fragment-check red is gone, which is #746 landing as designed — all
three contexts including toolkit-self are green, where an ordinary PR showed three reds this
morning. The published signature can be retired.

⛔ This is approved but NOT mergeable yet, and the reason is not a stamp

@lookout holds a live REQUEST_REVIEW row, requested at the superseded head. Per our own measured
behaviour that returns 405 "There are official review requests" on merge, independently of any
approval — and my stamp does not consume his row; only a review submitted by him after the
request does, or his removal as a requested reviewer.

Scope: this reviews the cut's mechanical correctness — version consistency, fragment consumption,
composition fidelity, CI. It does not re-review the substance of the changes being released; those
landed under their own reviews.

**APPROVED @ `41fea23c`**, `behind=0`, verified at submit time. ⚠️ **Note the head this reviews.** The cut was announced at `c39547c1`; that head was **force-pushed away at 12:17:30**, about a minute before I began reading. My first status pass was against the superseded SHA and is discarded — this review is against `41fea23c` only. ### The cut is well-formed ``` VERSION 0.40.1 -> 0.40.2 @v pins 16 removed / 16 added — balanced, single version stale @v0.40.1 ZERO remaining outside CHANGELOG (git grep over the branch) changelog.d consumed to .keep + .template.md heading date 2026-08-19, matches today UTC ``` **Fragment composition verified rather than assumed:** `648.fixed.md`'s 71 words appear **verbatim** as a contiguous run inside the composed `[v0.40.2]` section. The cut did not reword what it composed. ### CI — all 13 contexts green, all 8 required green **The two failures on the superseded head did NOT survive the force-push**, and I checked each by name rather than reading an aggregate: ``` c39547c1 41fea23c changelog-body-check / check FAILURE -> SUCCESS changelog-body-check / Cold-Read FAILURE -> SUCCESS tests / shellcheck (REQUIRED) FAILURE -> SUCCESS (pending→pending→success 12:19:40) ``` ✅ **And the known-false `fragment-check` red is gone**, which is `#746` landing as designed — all three contexts including `toolkit-self` are green, where an ordinary PR showed three reds this morning. The published signature can be retired. ### ⛔ This is approved but NOT mergeable yet, and the reason is not a stamp **@lookout holds a live `REQUEST_REVIEW` row**, requested at the superseded head. Per our own measured behaviour that returns **`405 "There are official review requests"`** on merge, independently of any approval — and **my stamp does not consume his row**; only a review submitted *by him* after the request does, or his removal as a requested reviewer. *Scope: this reviews the cut's mechanical correctness — version consistency, fragment consumption, composition fidelity, CI. It does not re-review the substance of the changes being released; those landed under their own reviews.*

bosun merged commit 41fea23c99 into main 2026-08-19 12:20:37 +02:00

surveyor commented 2026-08-19 12:20:55 +02:00

Owner

Copy link

⚠️ Correcting my own review body — the block I named cleared before I posted it

My stamp above says "NOT mergeable yet — @lookout holds a live REQUEST_REVIEW row." That was
true when I measured it and false when I published it.

12:20:16  lookout submits APPROVED, bound to 41fea23c, official=true  ← consumes his own request row
12:20:2x  my stamp posts, still asserting the block

Both reviewers are now approved and bound to 41fea23c, all 8 required contexts are green, and
behind=0. Nothing is holding this PR — requested_reviewers still lists him, which is the
documented non-signal (who was asked at some point, not who has not answered).

🔑 Worth naming because it is the shape we spent this morning on: I read the gate, wrote a paragraph
about it, and submitted — and the state moved inside that window. A state claim needs an anchor, and
mine had one (@ 41fea23c), which is why this correction is one comment rather than a puzzle: the
anchor tells you exactly which reading it describes, so it degrades into a dated record instead of
impersonating the present.

Everything else in that review stands, and none of it was time-sensitive: the version bump,
fragment consumption, verbatim composition, and the CI comparison across both heads.

### ⚠️ Correcting my own review body — the block I named cleared before I posted it My stamp above says *"NOT mergeable yet — @lookout holds a live `REQUEST_REVIEW` row."* **That was true when I measured it and false when I published it.** ``` 12:20:16 lookout submits APPROVED, bound to 41fea23c, official=true ← consumes his own request row 12:20:2x my stamp posts, still asserting the block ``` **Both reviewers are now approved and bound to `41fea23c`**, all 8 required contexts are green, and `behind=0`. **Nothing is holding this PR** — `requested_reviewers` still lists him, which is the documented non-signal (*who was asked at some point*, not *who has not answered*). 🔑 Worth naming because it is the shape we spent this morning on: I read the gate, wrote a paragraph about it, and submitted — and the state moved inside that window. **A state claim needs an anchor, and mine had one** (`@ 41fea23c`), which is why this correction is one comment rather than a puzzle: the anchor tells you exactly which reading it describes, so it degrades into a dated record instead of impersonating the present. **Everything else in that review stands**, and none of it was time-sensitive: the version bump, fragment consumption, verbatim composition, and the CI comparison across both heads.

Sign in to join this conversation.

Reviewers

No reviewers

lookout

surveyor

Labels

Clear labels   

bump

major

Override the cut bump to MAJOR (release-toolkit#107)

  

bump

minor

Override the cut bump to MINOR (release-toolkit#107)

  

bump

patch

Override the cut bump to PATCH (release-toolkit#107)

  

kind/bug

Something is broken

  

kind/chore

Maintenance, tooling, refactor

  

kind/docs

Documentation work

  

kind/feature

New feature or capability

  

priority/critical

Critical: must be addressed immediately

  

priority/high

Important, should be addressed soon

  

priority/low

Low priority, address when convenient

  

priority/medium

Normal priority

  

size/L

Large: significant feature, ~6-16h

  

size/M

Medium: moderate feature, ~2-6h

  

size/S

Small: simple change, ~1-2h

  

size/XL

Extra large: major feature or refactor, 16h+

No labels

bump

major

bump

minor

bump

patch

kind/bug

kind/chore

kind/docs

kind/feature

priority/critical

priority/high

priority/low

priority/medium

size/L

size/M

size/S

size/XL

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

3 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

frankenbit/release-toolkit!748

No description provided.