Repository navigation
ci: release with release-please (MBL-2633) - #259
Open
sydneycollins-cio wants to merge 1 commit into
Open
sydneycollins-cio wants to merge 1 commit into
sydneycollins-cio wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sydneycollins-cio
marked this pull request as ready for review
October 23, 2026 14:16
This branch has not been deployed
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.
v5.3.0 never reached npm because package.json wasn't bumped before the release. This adds release-please, which keeps a release PR open on main that bumps package.json, the lockfile, lib/version.ts and CHANGELOG.md. Merging that PR tags the release, and the publish job in publish.yml runs npm publish in the same run.
Publishing stays in publish.yml so npm trusted publishing keeps working. Manually created releases still publish as before. CHANGELOG.md gets a 5.3.0 entry, and a dry run against this branch proposes 5.4.0 with #254.
Commit messages need conventional prefixes (feat, fix) to show up in a release.
🤖 Generated with Claude Code