Skip to content

KAFKA-19166 Fix RC tag in release script #19518

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

Merged
merged 1 commit into from
Apr 22, 2025

Conversation

mumrah
Copy link
Member

@mumrah mumrah commented Apr 19, 2025

The release script was pushing the RC tag off of a temporary branch that
was never merged back into the release branch. This meant that our RC
and release tags were detached from the rest of the repository.

This patch changes the release script to merge the RC tag back into the
release branch and pushes both the tag and the branch.

@github-actions github-actions bot added the small Small PRs label Apr 19, 2025
@mumrah
Copy link
Member Author

mumrah commented Apr 19, 2025

cc @frankvicky -- can you test these changes on a new RC?

@frankvicky
Copy link
Contributor

Hi @mumrah
I have cherry-picked this patch to my local branch and tried to run a new RC.
It appears that the patch introduces a merge operation during the push of a tag, which violates the branch rule.
Screenshot from 2025-04-20 14-59-38

@showuon
Copy link
Member

showuon commented Apr 22, 2025

@frankvicky @mumrah , I just cherry-pick to 3.9 branch and ran the release script, the tag showed correctly in github now. So I think this PR fixes the problem. I'll merge this PR and rebuild a RC. Thanks.

@showuon showuon merged commit 11904c7 into apache:trunk Apr 22, 2025
17 of 23 checks passed
showuon pushed a commit that referenced this pull request Apr 22, 2025
The release script was pushing the RC tag off of a temporary branch that
was never merged back into the release branch. This meant that our RC
and release tags were detached from the rest of the repository.

This patch changes the release script to merge the RC tag back into the
release branch and pushes both the tag and the branch.

Reviewers: Luke Chen <showuon@gmail.com>
@mumrah
Copy link
Member Author

mumrah commented Apr 22, 2025

thanks @showuon!

@frankvicky, if we see that error again, we might need to include "--ff-only" to the merge command to prevent the merge commit. You might be seeing that due to local Git settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
small Small PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants