Repository navigation
chore(main): release 1.14.0 - #497
Conversation
bd90a8f to
1d68f62
Compare
1d68f62 to
28bc9c7
Compare
wz-gsa
left a comment
There was a problem hiding this comment.
AI-assisted review (OpenCode), verified independently at head 28bc9c75937cdea3bdd314091119338b281618b7.
Approving. I verified the complete release range v1.13.0..0c5258e7 rather than reading only the generated changelog.
Range coverage is complete
git rev-list --count v1.13.0..0c5258e7 is 3, and all three appear in the changelog with correct classification:
| Commit | Subject | Type |
|---|---|---|
306906a5 |
give verify scripts a "could not check" verdict state (#460) | fix |
c9d22810 |
bump opencode kit to OpenCode 2.0.30 (#499) | fix |
0c5258e7 |
bump pinned Paseo CLI to 0.12.0 (#504) | feat |
No commit in the range is omitted, and no changelog line cites a commit outside it. There are no non-release-bearing commits in the range, so nothing was correctly-but-silently dropped either.
The 1.13.0 to 1.14.0 minor bump is correct, driven by the single feat. No ! marker and no BREAKING CHANGE: footer in any of the three. Worth noting one near-miss: #504's body discusses upstream Paseo breaking changes in prose, explaining they do not affect the kit. That text is in a body sentence rather than a footer, so release-please correctly treats this as minor.
All three cited SHAs exist, all three PRs are merged, each PR's mergeCommit.oid equals the cited SHA, and each title matches the changelog verbatim including scope.
Diff is release-automation only
One file, CHANGELOG.md, +13/-0, confirmed three ways. No kit spec, source file, test, or workflow touched. This matches the shape of the last four release PRs, all of which were CHANGELOG.md-only. This repo has no .release-please-manifest.json or version.txt and never has, so the single-file diff is expected for release-type: simple here.
Checks
I approved the two action_required workflow runs, which had never executed. Six of seven now pass, including all three required contexts: Conventional Commit Title, Python Lint & Test, and Pattern Validation.
Link Check fails but is continue-on-error: true and is not a required context. It failed identically on the 1.11.0, 1.12.0, 1.12.1, and 1.13.0 release PRs, so this is the known pre-existing pattern rather than a regression from this release.
Branch is up to date with main.
Downstream note
This release is the prerequisite for bumping quickstart's PATTERNS_KIT_REF, which still points at v1.12.0 and therefore delivers Paseo 0.10.2 and OpenCode 2.0.22 to every user on quickstart main. A user is currently hitting the Paseo v2 stream defects that #504 fixes, so this release is on the critical path for that fix reaching anyone.
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
1.14.0 (2026-10-19)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.