chore(release): cut v14.2.0#226
Conversation
Manual release cut. release-please could not parse the squash commits on main - its conventional-commit parser fails on parenthesized phrases in commit subjects - so it considered zero commits and never proposed this release. This commit applies the exact bumps release-please would have made: package.json and package-lock 14.1.0 to 14.2.0, .release-please-manifest.json, and a CHANGELOG section for 14.2.0 in the generated format. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Caution Review failedPull request was closed or merged during review No actionable comments were generated in the recent review. π βΉοΈ Recent review infoβοΈ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: β Files ignored due to path filters (1)
π Files selected for processing (3)
π WalkthroughWalkthroughThis PR bumps the project version from 14.1.0 to 14.2.0 across release manifests and adds a corresponding changelog entry documenting new features (task relations, socket synchronization, activity history) and CI/lint updates. ChangesVersion 14.2.0 Release
Estimated code review effortπ― 1 (Trivial) | β±οΈ ~3 minutes Poem
π₯ Pre-merge checks | β 5β Passed checks (5 passed)
βοΈ Tip: You can configure your own custom pre-merge checks in the settings. β¨ Finishing Touchesπ§ͺ Generate unit tests (beta)
Comment |
Summary
Manual cut of v14.2.0 β the exact bumps release-please would have made:
package.json+package-lock.json14.1.0 β 14.2.0,.release-please-manifest.json, and a CHANGELOG section in the generated format (task relations feature + the two CI changes).Why manual
release-please ran successfully on every main push but parsed zero commits: its conventional-commit parser fails on parenthesized phrases in squash subjects (both
feat(tasks): β¦ (blocks / duplicates / relates) (#224)and the #222 promotion body tripped it), so it never proposed a release. Logs: see the Release workflow runs for commits 07392b0 / 68fa8fe.Updating the manifest here keeps release-please consistent β its next run will compute from 14.2.0.
After merge
The v14.2.0 tag + GitHub release will be created immediately (notes from the CHANGELOG section), which also triggers the Docker workflow to publish the semver images (
v14.2.0,14.2,14,latest).Lesson captured for the team
Keep squash-commit subjects on main simple β no parentheses or slashes in the description part β or release-please silently skips them.
π€ Generated with Claude Code
Summary by CodeRabbit
New Features
Infrastructure