Repository navigation
Fix tagpr release tag and publishing trigger - #18
Merged
Merged
Conversation
Konboi
force-pushed
the
fix/tagpr-release-trigger
branch
from
September 25, 2026 02:54
fc18840 to
26e21a0
Compare
Konboi
force-pushed
the
fix/tagpr-release-trigger
branch
from
September 25, 2026 02:58
26e21a0 to
f53392a
Compare
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
1 participant
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.
Why
tagpr created
launchable-testng-/1.4.3, which is not the intended path-style tag format. In addition, the default GitHub Actions token does not trigger the separate Maven Central publishing workflow when it pushes a tag.What
launchable-testng/<version>, which matches tagpr's prefix semantics.TAGPR_TOKENfine-grained PAT for tagpr checkout and API calls so its tag push triggers publishing.