-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 Determine release type from tag to also handle beta releases #10324
🌱 Determine release type from tag to also handle beta releases #10324
Conversation
287ef9c
to
be36cc6
Compare
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great to me! I think this would be an awesome improvement to the release notes tool. Thanks for working on this change 🚀
Just one tiny nit from me, nothing blocking!
be36cc6
to
04f9fce
Compare
🤔 Isn't it possible to determine if we have a beta/rc release from the release tag we pass in? But totally fair to keep this as a parameter :-) |
This is possible, sure. After taking a deeper look into the code we can easily use semver for this 👍🏻 |
04f9fce
to
cc396e6
Compare
8c37713
to
9bddc42
Compare
9bddc42
to
ffefe11
Compare
11c68f1
to
ff24342
Compare
we also have release docs with example usage: https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#create-pr-for-release-notes these should be updated too (its a small change, release team can take as a follow up if we don't make the update in this pr) |
This is already part of this PR, see https://github.com/kubernetes-sigs/cluster-api/pull/10324/files#diff-751bae1afb6862debc4d8d6b2d39bba9d2838e720c37c8b2805138c738843025 |
Signed-off-by: Tobias Giese <[email protected]>
ah beautiful! missed that, thanks @tobiasgiese /lgtm |
LGTM label has been added. Git tree hash: 68c316f2fbe03f6f03b76e9ffb6d1860630e96b2
|
ff24342
to
758b610
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Nice work!
LGTM label has been added. Git tree hash: 5cf60e1ea2f29c7e902fb1c1e78ffdbc1b445a3c
|
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cahillsf 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:
Approvers can indicate their approval by writing |
/hold |
// Error handling can be ignored as the version has been validated in computeConfigDefaults already. | ||
newTag, _ := semver.ParseTolerant(newTagConfig) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One last question: is it fair to ignore the error handling here? Or should we handle it anyway?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Talked to @chrischdi, totally fair to do it like this. It will not panic if the version cannot be parsed.
/unhold |
What this PR does / why we need it:
Currently the tool prints the same warning for both beta and rc releases.
This PR removes the parameter
--pre-release-version
and let the binary determine from the given tag what type of release it is.Related to #10323
/area release