Skip to content

Fix release notes generated for rc.0 tag #12277

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.

Sign up for GitHub

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

Jump to bottom
Open
Tracked by #12123
chandankumar4 opened this issue May 23, 2025 · 1 comment
Open
Tracked by #12123

Fix release notes generated for rc.0 tag #12277

chandankumar4 opened this issue May 23, 2025 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@chandankumar4
Copy link
Contributor

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.
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 23, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@cprivitere cprivitere mentioned this issue May 23, 2025
Open
42 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
CAPI v1.11 release improvement tasks
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@k8s-ci-robot @chandankumar4