fix: add ESR support to release calendar script#25205
Merged
Merged
Conversation
The update-release-calendar.sh script did not account for Extended Support Release (ESR) versions. Running it would drop ESR entries (e.g. 2.24) from the calendar or mark them as "Not Supported" instead of "Extended Support Release". Changes: - Add ESR_VERSIONS array for tracking active ESR minor versions - Add is_esr_version() helper to check ESR membership - Extract generate_release_row() to reduce duplication - Prepend ESR versions older than the standard window - Override "Not Supported" status for ESR versions in the window
Regenerated via `scripts/update-release-calendar.sh`. ## Updates **Release calendar (`docs/install/releases/index.md`):** - 2.33 is now Mainline, 2.32 is Stable, 2.31 is Security Support - Latest patch versions updated across all releases - 2.24 and 2.29 correctly marked as Extended Support Release **Kubernetes and Rancher docs:** - Update `docs/install/kubernetes.md` mainline 2.30.0 -> 2.33.2, stable 2.29.5 -> 2.32.1 - Update `docs/install/rancher.md` mainline 2.30.0 -> 2.33.2, stable 2.29.5 -> 2.32.1 Depends on #25205. <!-- This PR was authored by Coder Agents -->
f0ssel
added a commit
that referenced
this pull request
May 12, 2026
Replace the Go CLI's update-docs subcommand with a call to the existing scripts/update-release-calendar.sh bash script, which regenerates the release calendar from git tags (including ESR support). This eliminates duplicate calendar-update logic and aligns with the approach in #25205. The update-docs job no longer needs Go setup, only Node (for markdown table formatting via make fmt/markdown which the script calls).
Shelnutt2
approved these changes
May 13, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
The
update-release-calendar.shscript did not account for Extended Support Release (ESR) versions. Running it would drop ESR entries (e.g. 2.24) from the calendar entirely or mark them as "Not Supported" instead of "Extended Support Release".Changes
ESR_VERSIONSarray for tracking active ESR minor versionsis_esr_version()helper to check ESR membershipgenerate_release_row()to reduce duplicationNote
When new ESR versions are designated or old ones reach end of life, update the
ESR_VERSIONSarray at the top of the script.