CLOUDP-291238: Fix release tagging by making it manual #2024
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.
Ever since
tag.yml
was added with the idea to automate the tagging of a release, it was failed on every single release afterwards. Each fix to it would just turn into a different bug in the next release.Given this track record and the fact we do not yet have a reliable way to dry run releases that would allow us to automate this step reliably, lets just for now make the step manual and document it accordingly. This manual step is what has been used actually on the releases when the automation failed and is the standard way most projects cut their releases anyways.
All Submissions: