Skip to content

[release-3.6] Update release script to exactly match the target tag#19951

Merged
ahrtr merged 1 commit intoetcd-io:release-3.6from
ahrtr:release_script_20250515
May 15, 2025
Merged

[release-3.6] Update release script to exactly match the target tag#19951
ahrtr merged 1 commit intoetcd-io:release-3.6from
ahrtr:release_script_20250515

Conversation

@ahrtr
Copy link
Copy Markdown
Member

@ahrtr ahrtr commented May 15, 2025

When we release etcd v3.6.0, we ran into an issue. The command git tag --list | grep -c "${RELEASE_VERSION}")" -gt 0 returned 64, so it thought the tag v3.6.0 already existed, but actually not.

So updating the script to exactly match the target tag.

Normally we fix in main, and backport to stable releases, given the tight schedule, so we fix it release-3.6 for now, and backport and forward port to other branches.

Copy link
Copy Markdown
Member

@jmhbnz jmhbnz left a comment

Choose a reason for hiding this comment

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

LGTM - We validated this during the release call. Thanks @ahrtr

@k8s-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahrtr, jmhbnz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ahrtr
Copy link
Copy Markdown
Member Author

ahrtr commented May 15, 2025

Normally we fix in main, and backport to stable releases, given the tight schedule, so we fix it release-3.6 for now, and backport and forward port to other branches.

@joshjms will followup this, thx

@ahrtr
Copy link
Copy Markdown
Member Author

ahrtr commented May 15, 2025

To be clearer, the command below returned 64, so it's greater than 0

git tag --list | grep -c "${RELEASE_VERSION}")"

@ahrtr ahrtr force-pushed the release_script_20250515 branch from 888b65e to 6ff112e Compare May 15, 2025 19:12
Signed-off-by: Benjamin Wang <benjamin.ahrtr@gmail.com>
@ahrtr ahrtr force-pushed the release_script_20250515 branch from 6ff112e to a1bcdc7 Compare May 15, 2025 19:25
@ahrtr ahrtr merged commit f5d605a into etcd-io:release-3.6 May 15, 2025
7 of 26 checks passed
@ahrtr ahrtr mentioned this pull request May 15, 2025
@joshjms
Copy link
Copy Markdown
Member

joshjms commented May 15, 2025

/cherrypick release-3.4

@k8s-infra-cherrypick-robot
Copy link
Copy Markdown

@joshjms: new pull request created: #19953

Details

In response to this:

/cherrypick release-3.4

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@joshjms
Copy link
Copy Markdown
Member

joshjms commented May 15, 2025

/cherrypick release-3.5

@k8s-infra-cherrypick-robot
Copy link
Copy Markdown

@joshjms: new pull request created: #19954

Details

In response to this:

/cherrypick release-3.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@joshjms
Copy link
Copy Markdown
Member

joshjms commented May 15, 2025

/cherrypick main

@k8s-infra-cherrypick-robot
Copy link
Copy Markdown

@joshjms: new pull request created: #19955

Details

In response to this:

/cherrypick main

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@ahrtr ahrtr deleted the release_script_20250515 branch May 16, 2025 09:06
@ivanvc ivanvc mentioned this pull request May 28, 2025
4 tasks
@ivanvc ivanvc mentioned this pull request Jul 6, 2025
2 tasks
@ivanvc ivanvc mentioned this pull request Feb 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

5 participants