Repository navigation
feat(release): release:prepare adds the release to the pull request of the changes - #300
Merged
Merged
Conversation
…f the changes A release needed two reviews: the pull request of the changes, then the chore(release) one. Run on the branch of the changes, release:prepare now commits the version bumps there, pushes them and adds the release notes to that branch's pull request (opened if there is none), so the changes and their release are approved together. It asks before adding the commit to an approved pull request, and stops when the release is already prepared on the branch or the branch lacks the latest main. Run on main it still opens a release pull request of its own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cl-mvezzelli
approved these changes
Oct 26, 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.
Next changes to main
A draft pull request that collects the next changes to main, so they get one review. The title follows the contents. It is marked ready for review, and the reviewers are requested, when it is complete.
Changes
feat(release): one review for a change and its release. Until now a release needed two approved PRs: the one with the changes, then thechore(release)one with the versions.Run on the branch of the changes,
pnpm release:preparenow:Releasesection that a new run replaces, keeping the rest of the description. If the branch has no pull request, it opens one, titled after the branch's first change.It stops in these cases:
Run on
main, it still opens a release PR of its own, for changes that were merged without a release.Verification
On a local throwaway branch, never pushed, with a
feat(tags)commit:--dry-run--no-prchore(release): tags-v3.1.0commit added to the branchmainRelease package: 29 tests passing (3 new, for the PR description section). Type-check and
pnpm lintpass.🤖 Generated with Claude Code
Release
Merging this pull request publishes these versions: publish.yml tags them, publishes them to npm and publishes their GitHub releases.
@commercelayer/cli-plugin-tags3.0.0 → 3.0.1 (tags-v3.0.1)Release notes
@commercelayer/cli-plugin-tags 3.0.1
3.0.1 (2026-10-26)
Maintenance release: no changes to features or fixes since tags-v3.0.0 (tests, tooling, dependencies).