Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLOUDP-291238: Fix release tagging by making it manual #2024

Merged
merged 1 commit into from
Jan 7, 2025

Conversation

josvazg
Copy link
Collaborator

@josvazg josvazg commented Jan 7, 2025

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:

  • Have you signed our CLA?

Copy link
Collaborator

@igor-karpukhin igor-karpukhin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks way simpler 👍

@josvazg josvazg merged commit 5d3a4db into main Jan 7, 2025
9 checks passed
@josvazg josvazg deleted the CLOUDP-291238/fix-release-tagging branch January 7, 2025 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants