Repository navigation
Conversation
When pushing a tag fails, TagBot opens an issue with commands to tag and release the version by hand. Those commands used the bare version, so for a subpackage they created `v1.0.0` instead of `Foo-v1.0.0`, and checked for the wrong tag when deciding whether only the release was missing.
maleadt
force-pushed
the
tb/manual-tag-prefix
branch
from
November 17, 2026 10:32
2112b6e to
6896561
Compare
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.
If pushing a tag fails, TagBot opens an issue with commands for tagging and releasing the version by hand. Those commands used the bare version, so for a subpackage they created and released
v1.0.0instead ofFoo-v1.0.0. The check for an existing tag, which decides whether only the release is missing, used the bare version too.The commands and the version list in the issue now use the package's tag name.
This touches the same lines as #611; I'll rebase whichever PR merges second.