feat(gha): pass version as cloudsmith tags #12175
Merged
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.
(cherry picked from commit 851ebcf5e65d6ba12aa5026a453e10f978f95ceb)
Summary
This is the sister PRs:
It will allow the
version
input to therelease.yml
workflow to be passed as a Cloudsmith tag when uploading packages (assuming it meets the criteria). This will in turn allow us to keep better track of special packages in Cloudsmith, like the recentrc
packages.An existing example of such a tag is the
fips
tag: https://cloudsmith.io/~kong/packages/?q=tag%3AfipsFor this to work, the input must contain:
rc
,alpha
,beta
, ornightly
And cannot contain characters outside of:
a-zA-Z0-9._,
So an input like "3.0.0.0-rc.3" will work, but an input like "3.0.0.0-gamma.5", "9.9.9.isa%is%cool", or "3.5.0.0+1" will not.
Here's an example of what this looks like on the Cloudsmith side of things (input was
3.6.0.0.rc.0
): https://cloudsmith.io/~kong/packages/?q=tag%3A3.6.0.0.rc.0Checklist
changelog/unreleased/kong
orskip-changelog
label added on PR if changelog is unnecessary. README.mdIssue reference
Fix #KAG-3299