Repository navigation
chore(main): release 4.0.0 - #445
Conversation
f1d1fc2 to
5923159
Compare
7a4259d to
373c337
Compare
a4ff459 to
3059b84
Compare
cef828f to
f140bce
Compare
|
AI-assisted review (OpenCode), advisory. Reviewed the release-please output against what actually merged, which is the only check worth doing on a release PR. The version bump and 21 of the 25 entries are right. Two are missing, and the reason is a repo setting rather than anything in this PR. What's missingDiffed the PR numbers in the changelog against Two of those four are correctly omitted — release-please hides these types by default and they're not user-facing:
The other two are silently dropped, not hidden:
Root cause: the PR-title gate and release-please read different things
With The fix is one repo setting, not a code change: That makes the squash subject always equal the title the gate already validated, which closes the gap by construction rather than by reviewer vigilance. Worth applying to On this PR specificallyI wouldn't hold 3.2.0 for it — the two missing entries are a README tweak and one allowlist addition, and re-cutting the changelog by hand risks more than it fixes. But the Everything else checks out: Method: |
5dbc2b7 to
30fc2e8
Compare
30fc2e8 to
dc25978
Compare
tau-gov
left a comment
There was a problem hiding this comment.
Two user-facing changes merged after v3.1.0 are absent from the generated 3.2.0 notes. The repository now uses PR_TITLE for squash commits, which should prevent recurrence, but these existing omissions still need to be restored in this release.
7b2cc62 to
098d886
Compare
098d886 to
1b21b71
Compare
|
Hold this release PR until #549 lands. #474's squash commit/release notes describe the full collapsed kit stack (patterns v1.12.0, OCI opt-in, no native OpenCode fallback), but the final merged code only included the lower #474 layer. #549 lands the missing implementation so release notes and shipped behavior match. |
|
Addressed the two durable release-note omissions at the source metadata level rather than hand-editing generated CHANGELOG output. Added release-please commit override blocks to the merged PR bodies:
These should be picked up the next time release-please regenerates this PR, so the edits won’t be blown away. I could not manually dispatch the Release workflow from this token ( |
1b21b71 to
6af97b9
Compare
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
4.0.0 (2026-10-06)
⚠ BREAKING CHANGES
acq configure,--kit, orACQ_EXTRA_KITS.Features
acq configureUI for extra kits + token-scoping defaults (#500) (13d9d3a)Bug Fixes
This PR was generated with Release Please. See documentation.