🐛 Set previous release tag version for RELEASE CANDIDATE/BETA RELEASE

[chandankumar4]

What this PR does / why we need it:

• Add Previous release tag version for RELEASE CANDIDATE/BETA RELEASE

For RELEASE CANDIDATE/BETA RELEASE

$ RELEASE_TAG=v1.7.0-rc.1 PREVIOUS_VERSION_TAG=tags/v1.7.0-rc.0 make release-notes

go build -C hack/tools -o /Users/ckumar14/go/src/github.com/sigs.k8s.io/cluster-api/bin/notes -tags tools sigs.k8s.io/cluster-api/hack/tools/release/notes
./bin/notes --release v1.7.0-rc.1 --previous-release-version tags/v1.7.0-rc.0 > CHANGELOG/v1.7.0-rc.1.md
2024/04/14 10:46:08 Computing diff between v1.7.0-rc.0 and heads/release-1.7
2024/04/14 10:46:08 Calling endpoint repos/kubernetes-sigs/cluster-api/compare/v1.7.0-rc.0...release-1.7?per_page=250&page=1&
2024/04/14 10:46:09 Total of 1 pages and 31 elements read
2024/04/14 10:46:09 Reading ref heads/release-1.7 for upper limit
.....

For Release TAG

$ RELEASE_TAG=v1.7.0 make release-notes

go build -C hack/tools -o /Users/ckumar14/go/src/github.com/sigs.k8s.io/cluster-api/bin/notes -tags tools sigs.k8s.io/cluster-api/hack/tools/release/notes
./bin/notes --release v1.7.0 --previous-release-version "" > CHANGELOG/v1.7.0.md
2024/04/14 10:56:07 Computing diff between tags/v1.6.0 and heads/release-1.7
2024/04/14 10:56:07 Calling endpoint repos/kubernetes-sigs/cluster-api/compare/v1.6.0...release-1.7?per_page=250&page=1&
2024/04/14 10:56:09 Calling endpoint repos/kubernetes-sigs/cluster-api/compare/v1.6.0...release-1.7?per_page=250&page=2&
.....

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #10396

[k8s-ci-robot]

Hi @chandankumar4. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[sbueringer]

@chandankumar4 do you have time to address the findings?

[chandankumar4]

@chandankumar4 do you have time to address the findings?

Sure, Sorry I totally missed this PR, I'll update the PR. Thanks

[chandankumar4]

@chandankumar4 do you have time to address the findings?

I have resolved the review comment, @sbueringer do you have time to look at it once? Thanks

[chandankumar4]

/ok-to-test

[k8s-ci-robot]

@chandankumar4: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

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.

[sbueringer]

/ok-to-test

[sbueringer]

@chandankumar4 Looks like we also have a linter finding: https://github.com/kubernetes-sigs/cluster-api/actions/runs/10268177616/job/28410554105?pr=10435

[chandankumar4]

@chandankumar4 Looks like we also have a linter finding: https://github.com/kubernetes-sigs/cluster-api/actions/runs/10268177616/job/28410554105?pr=10435

Yes, I have it resolved

[sbueringer]

Thx!

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 759c98aadb699900060f54621393a19f602be831

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sbueringer]

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