Issue with k8s.io/releases/ - Patch Releases field is inconsistent

[jsoref]

Release History

1.35

Latest Release:1.35.0 (released: 2025-12-17)
End of Life:2027-02-28
Patch Releases: n/a
Complete 1.35 Schedule and Changelog

1.34

Latest Release:1.34.2 (released: 2025-11-11)
End of Life:2026-10-27
Patch Releases: 1.34.0, 1.34.1, 1.34.2
Complete 1.34 Schedule and Changelog

1.33

Latest Release:1.33.6 (released: 2025-11-11)
End of Life:2026-06-28
Patch Releases: 1.33.1, 1.33.2, 1.33.3, 1.33.4, 1.33.5, 1.33.6
Complete 1.33 Schedule and Changelog

1.32

Latest Release:1.32.10 (released: 2025-11-11)
End of Life:2026-02-28
Patch Releases: 1.32.0, 1.32.1, 1.32.2, 1.32.3, 1.32.4, 1.32.5, 1.32.6, 1.32.7, 1.32.8, 1.32.9, 1.32.10
Complete 1.32 Schedule and Changelog

---

So:

1. 1.32 lists 1.32.0 as a patch release
2. 1.33 does not list 1.33.0 as a patch release
3. 1.34 lists 1.34.0 as a patch release
4. 1.35 does not list 1.35.0 as a patch release (and there is no 1.35.1)

---

Related:

https://kubernetes.io/releases/patch-releases/#1-35 does not list 1.35.0, although https://github.com/kubernetes/kubernetes/releases/tag/v1.35.0 exists.

1.34 on that page has a 1.34.0, 1.33 on that page does not have a 1.33.0, and 1.32 on that page does have a 1.32.0.

---

Note that neither page makes any reference to even/odd cadence.

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

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

Details

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.

[lmktfy]

/language en
/sig release

and IMO
/priority backlog

[jsoref]

I can't tell if this content is auto-generated, guided by a process, or purely manual.

If it's purely manual,and if someone is willing to help me get a PR merged to fix this, I'd be willing to write one.

[lmktfy]

It's automatically rendered from data inside data/releases.

Proposals (pull requests)to clean up the https://github.com/kubernetes/website/tree/main/data/releases data are welcome.

[jsoref]

• https://github.com/kubernetes/website/pull/49008/changes added 1.32.0
• https://github.com/kubernetes/website/pull/50478/changes added 1.33.1 w/o 1.33.0
• https://github.com/kubernetes/website/pull/52269/changes added 1.34.0
• https://github.com/kubernetes/website/pull/53663/changes added 1.35.1 w/o 1.35.0

[Aryan-Bagale]

The data was generated using the "schedule-builder" tool PR #53697 was opened to address issue #53692. This new issue appears to be covered by the same change.

[jsoref]

This issue is about the missing .0 releases and the fact that there's apparently a process hole that causes them to be missed sporadically.

• Update "data/releases/schedule.yaml" for Dec 2025 patches #53697 will not fix this issue.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[jsoref]

/remove-lifecycle stale