schedule-builder: fix EOL branches without a next release - #4510
Merged
Conversation
kubernetes-prow
Bot
added
the
release-note
kubernetes-prow
Bot
added
the
kind/bug
kubernetes-prow
Bot
added
needs-priority
cncf-cla: yes
kubernetes-prow
Bot
added
approved
Member
Author
|
@saschagrunert Fixed, PTAL. |
Member
Lint CI is not green unfortunately. |
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
saschagrunert
approved these changes
Aug 31, 2026
kubernetes-prow
Bot
added
the
lgtm
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saschagrunert, xmudrii The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind bug
What this PR does / why we need it:
schedule-builderskipped release branches with nonextpatch release before ever checking their end of life date, so branches whose final patch already shipped (e.g. 1.33) were never moved toeol.yaml. The end of life check now runs first, falling back to the newestpreviousPatchesentry and the scheduledendOfLifeDate.Which issue(s) this PR fixes:
None
Does this PR introduce a user-facing change?
/assign @saschagrunert @cpanato @puerco
cc @kubernetes/release-engineering