Release use versions from git tags instead of static value #1002
+32
−14
Conversation
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
shijiesheng
requested review from
Groxx,
abhishekj720,
demirkayaender,
dkrotx,
natemort and
taylanisikdemir
as code owners
natemort
approved these changes
May 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What changed?
Why?
Release rc versions requires code commits which slows down the release process.
Now tagging a value would just release rc version easily
Future Plan
If everything looks good, we can change the action to closeAndRelease directly.
How did you test it?
Sample run
https://github.com/shijiesheng/cadence-java-client/actions/runs/15219317469/job/42811806456
Repository is correctly closed.
Potential risks
Release notes
Documentation Changes