Skip to content

Update release schedule after 1.21 release#1759

Merged
knative-prow[bot] merged 1 commit intoknative:mainfrom
linkvt:update-release-schedule-after-1.21
Feb 4, 2026
Merged

Update release schedule after 1.21 release#1759
knative-prow[bot] merged 1 commit intoknative:mainfrom
linkvt:update-release-schedule-after-1.21

Conversation

@linkvt
Copy link
Contributor

@linkvt linkvt commented Jan 29, 2026

Knative 1.21 was released on 2026-01-27. This updates the schedule to reflect the new release state and corrects EOL date calculations.

Changes

  • Move 1.21 from upcoming to supported releases
  • Add 1.24 to upcoming releases (Oct 2026, K8s 1.35)
  • Fix EOL dates for 1.19 and 1.20 per n+2 + 1 week formula

/cc @gauron99

@knative-prow knative-prow bot requested a review from gauron99 January 29, 2026 11:04
@knative-prow knative-prow bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jan 29, 2026
linkvt added a commit to linkvt/knative-release that referenced this pull request Jan 29, 2026
Aligns release dates with knative/community#1759:
- v1.21 released 2026-01-27 (was 2026-01-20)
- v1.22 scheduled for 2026-04-28 (was 2026-04-21)
- Added v1.24 for 2026-10-27

Changes:
- Correct v1.21 and v1.22 release dates
- Add v1.24 release to schedule
- Update PKG cut and unpin dates accordingly

Signed-off-by: Vincent Link <vlink@redhat.com>
@linkvt linkvt force-pushed the update-release-schedule-after-1.21 branch from 781e7f9 to c0c573c Compare January 29, 2026 11:22
@gauron99
Copy link
Contributor

/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jan 29, 2026
@gauron99
Copy link
Contributor

/approve

@gauron99
Copy link
Contributor

@dprotaso PTAL

@linkvt
Copy link
Contributor Author

linkvt commented Jan 30, 2026

By the way, if we want to wait with this PR until Tuesday next week I could also already move 1.19 down to unsupported.

@dprotaso
Copy link
Member

I'm good to wait till next Tuesday

Knative 1.21 was released on 2026-01-27. This updates the schedule
to reflect the new release state and corrects EOL date calculations.

Changes:
- Move 1.21 from upcoming to supported releases
- Move 1.19 to No longer supported releases
- Add 1.24 to upcoming releases (Oct 2026, K8s 1.35)
- Fix EOL dates for 1.19 and 1.20 per n+2 + 1 week formula

Signed-off-by: Vincent Link <vlink@redhat.com>
@linkvt linkvt force-pushed the update-release-schedule-after-1.21 branch from c0c573c to 10008cc Compare January 30, 2026 18:05
@knative-prow knative-prow bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 30, 2026
@gauron99
Copy link
Contributor

gauron99 commented Feb 3, 2026

@dprotaso could you please approve?

@dprotaso
Copy link
Member

dprotaso commented Feb 4, 2026

/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Feb 4, 2026
@linkvt
Copy link
Contributor Author

linkvt commented Feb 4, 2026

@dprotaso not sure if you didn't /approve but /lgtm on purpose :)

@dprotaso
Copy link
Member

dprotaso commented Feb 4, 2026

/approve

@knative-prow
Copy link

knative-prow bot commented Feb 4, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, gauron99, linkvt

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 4, 2026
@knative-prow knative-prow bot merged commit 09d5b67 into knative:main Feb 4, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants