Fix release notes generated for rc.0 tag

[chandankumar4]

What steps did you take and what happened?

Release noted generated for v1.10.0-rc.0 is generated by comparing the changes between tags/v1.9.0 and heads/main But it should be between tags/v1.9.0 and heads/release-1.10.

Adding branch here fixed the issue, for ex: --branch release-1.10. So the branch name should be dynamics, probably we can use variable RELEASE_TAG to generate release branch.

What did you expect to happen?

It should Computing diff between tags/v1.9.0 and heads/release-1.10

Cluster API version

v1.10

Kubernetes version

No response

Anything else you would like to add?

No response

Label(s) to be applied

/kind bug
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

[chrischdi]

/help

[k8s-ci-robot]

@chrischdi:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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.

[neoaggelos]

/assign