GHA-290 Fix publish-github-release: strip build suffix from release title#149
Merged
kirill-knize-sonarsource merged 1 commit intoMay 11, 2026
Merged
Conversation
Contributor
SummaryThis PR fixes GitHub release creation to strip build metadata from release titles while preserving the full version in git tags. The problem: When a version includes build metadata (e.g., The solution:
This ensures releases display nicely in GitHub while maintaining technically accurate git tags. What reviewers should knowKey change to review:
What to verify:
Testing considerations:
|
2bad8e0 to
54d12a1
Compare
|
damien-urruty-sonarsource
approved these changes
May 11, 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.



Release title was incorrectly containing the build number like
5.2.3+12345.Now it is correct with just
5.2.3.