chore(release): release new version v14.3.0#250
Merged
Conversation
Manual release cut: #240 was squash-merged as a single chore commit, so release-please found no releasable commits on main. This mirrors what its Release PR would have produced - bumps package.json + the release-please manifest to 14.3.0 and adds the CHANGELOG section compiled from the PRs merged to staging since v14.2.0 (#228-#249). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
π WalkthroughWalkthroughVersion bumped from Changesv14.3.0 Release Bump
Estimated code review effortπ― 1 (Trivial) | β±οΈ ~2 minutes Possibly related PRs
Poem
π₯ Pre-merge checks | β 4 | β 1β Failed checks (1 inconclusive)
β Passed checks (4 passed)
βοΈ Tip: You can configure your own custom pre-merge checks in the settings. β¨ Finishing Touchesπ Generate docstrings
π§ͺ Generate unit tests (beta)
Comment |
joshishiv4
approved these changes
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cuts v14.3.0.
Why this is manual: #240 (the staging->main promotion) was squash-merged into a single
chore(release): promote staging to maincommit, so release-please found no releasable commits onmainand opened no Release PR (hence no tag). This PR mirrors exactly what its Release PR would have produced:package.json14.2.0 -> 14.3.0.release-please-manifest.json-> 14.3.0 (keeps release-please consistent for the next cycle)CHANGELOG.mdβ full 14.3.0 section compiled from the PRs merged tostagingsince v14.2.0 (feat(tier1): add reactions, recents, auto-archive, burndown and relation alertsΒ #228-fix: address safe CodeRabbit findings from the #240 promotion reviewΒ #249), grouped into Features / Bug Fixes / DocumentationAfter this merges, the
v14.3.0git tag + GitHub Release (with the changelog as the body) will be created.Going forward, promote
staging -> mainwith a merge commit (never squash) so release-please sees the conventional commits and auto-tags.π€ Generated with Claude Code
Summary by CodeRabbit