Skip to content

chore(main): release 1.14.0 - #497

Merged
wz-gsa merged 1 commit into
mainfrom
release-please--branches--main
Oct 20, 2026
Merged

wz-gsa merged 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.14.0 (2026-10-19)

Features

  • paseo: bump pinned Paseo CLI to 0.12.0 (#504) (0c5258e)

Bug Fixes

  • acq-kits: bump opencode kit to OpenCode 2.0.30 (#499) (c9d2281)
  • acq-kits: give verify scripts a "could not check" verdict state (#460) (306906a)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot requested a review from a team as a code owner October 15, 2026 18:09
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from bd90a8f to 1d68f62 Compare October 17, 2026 23:37
@github-actions github-actions Bot changed the title chore(main): release 1.13.1 chore(main): release 1.14.0 Oct 19, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 1d68f62 to 28bc9c7 Compare October 19, 2026 19:24

@wz-gsa wz-gsa left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@wz-gsa
wz-gsa merged commit 89e87f9 into main Oct 20, 2026
6 of 7 checks passed
@wz-gsa
wz-gsa deleted the release-please--branches--main branch October 20, 2026 18:14
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant