Repository navigation
ci: drop the v from release names - #27
Merged
Merged
Conversation
Tags already have no v; release-please titled the GitHub release v0.0.2 by default. include-v-in-release-name only affects future releases. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.
Tags have no
v(0.0.2), but release-please titles the GitHub releasev0.0.2unlessinclude-v-in-release-nameis false (the option is in its config schema; default true). This makes the title match the tag from the next release on. It does not change existing releases, tags or download URLs.Release type is
ci:, so merging this does not open a release PR.🤖 Generated with Claude Code