GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing github.com — fix(docs): backport the release calendar and install version refresh for v2.39.0 by denisra · Pull Request #31716 · coder/coder

Conversation

denisra commented Nov 3, 2026

Copy link

Copy Markdown

Collaborator

Backport of #31715 to release/2.39, the branch the 2.39 docs line is built from. The docs site pins each line to its newest tag, so this goes live with v2.39.1.

🤖 Generated with Claude Code

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions


          docs: refresh the release calendar and install versions for v2.39.0

6cd16c3

Rotates the calendar for the November 3 releases: 2.39 mainline,
2.38 stable, 2.37 security support, 2.36 out of support, and the
newest patch per line (v2.38.6, v2.37.10, v2.36.12, v2.35.12,
v2.34.18, v2.29.26). Updates the Helm install examples and the
Rancher version picker to 2.39.0 mainline and 2.38.6 stable, and
the latest-ESR link to v2.34.18.

Co-Authored-By: Claude Fable 5 <[email protected]>

github-actions Bot assigned denisra

Nov 3, 2026

denisra requested review from b-coder-b and nickvigilante

November 3, 2026 20:48

nickvigilante approved these changes

Nov 3, 2026

View reviewed changes

coderagents Bot reviewed

Nov 4, 2026

View reviewed changes

Comment thread

docs/reference/releases.md

		\| [2.36](https://coder.com/changelog/coder-2-36) \| August 04, 2026 \| Not Supported \| [v2.36.12](https://github.com/coder/coder/releases/tag/v2.36.12) \|
		\| [2.37](https://coder.com/changelog/coder-2-37) \| September 01, 2026 \| Security Support \| [v2.37.10](https://github.com/coder/coder/releases/tag/v2.37.10) \|
		\| [2.38](https://coder.com/changelog/broader-model-access-and-tighter-governance-controls-in-238) \| October 06, 2026 \| Stable \| [v2.38.6](https://github.com/coder/coder/releases/tag/v2.38.6) \|
		\| [2.39](https://coder.com/changelog/project-level-memory-for-coder-agents-in-239) \| November 03, 2026 \| Mainline \| [v2.39.0](https://github.com/coder/coder/releases/tag/v2.39.0) \|

coderagents Bot Nov 4, 2026

Copy link

Copy Markdown

Contributor

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.

Blocking: The calendar rotation advances mainline 2.38→2.39 but stops at the 2.39 Mainline row. (Cartographer)

The release-calendar generators (scripts/releaser/docs.go updateCalendar and scripts/update-release-calendar.sh) append a Not Released row for the next minor and trim the oldest Not Supported rows when mainline advances, as the v2.38 rotation (commit 2254965ef8) did by adding 2.39 Not Released and dropping 2.32. The v2.39 rotation here should add a 2.40 | Not Released | N/A row and trim the aged-out 2.33 row, so the table matches the documented generation process.

Suggested change

	\| [2.39](https://coder.com/changelog/project-level-memory-for-coder-agents-in-239) \| November 03, 2026 \| Mainline \| [v2.39.0](https://github.com/coder/coder/releases/tag/v2.39.0) \|
	\| [2.39](https://coder.com/changelog/project-level-memory-for-coder-agents-in-239) \| November 03, 2026 \| Mainline \| [v2.39.0](https://github.com/coder/coder/releases/tag/v2.39.0) \|
	\| 2.40 \| \| Not Released \| N/A \|

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

coderagents Bot commented Nov 4, 2026

Copy link

Copy Markdown

Contributor

Documentation Check

Blocking

docs/reference/releases.md (open) - The calendar rotation ends at 2.39 Mainline with no 2.40 Not Released successor row and still lists the aged-out 2.33 row; regenerate to match scripts/releaser/docs.go / scripts/update-release-calendar.sh.

Design notes

The release calendar row set no longer matches what the release-calendar generators (scripts/releaser/docs.go updateCalendar, scripts/update-release-calendar.sh) produce after mainline advances.

Related open PRs

docs: refresh the release calendar and install versions for v2.39.0 #31715 is the same refresh on main and is still open.

Findings for agents

- id: coverage-releases-calendar-window
  persona: coverage
  class: wrong
  blocking: true
  file: docs/reference/releases.md
  line: 96
  quote: "| [2.39](https://coder.com/changelog/project-level-memory-for-coder-agents-in-239)                | November 03, 2026  | Mainline                 | [v2.39.0](https://github.com/coder/coder/releases/tag/v2.39.0)   |"
  evidence:
    - scripts/releaser/docs.go:updateCalendar (appends a Not Released row for nextMinor, then trims oldest Not Supported to maxRows=8)
    - scripts/update-release-calendar.sh:generate_release_calendar (start_minor = latest_minor - 5)
  rule: null
  problem: "The release calendar advances mainline 2.38->2.39 but the rotation stops at the 2.39 Mainline row: it does not add the next-milestone 'Not Released' row (2.40) that the release-calendar generators append, and it keeps the aged-out 2.33 'Not Supported' row that those generators trim. A reader sees the calendar end at 2.39 with no upcoming release, which is not what the documented generation process produces."
  fix: "Regenerate the release calendar (scripts/update-release-calendar.sh, or scripts/release.sh) and commit the result so it appends a '2.40 | Not Released | N/A' row and trims the 2.33 row, matching the v2.38 rotation in 2254965ef8."
  verified: true

Automated review via Coder Agents. Reply to a finding's thread with the reason if the finding is wrong.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.


          docs: add the 2.40 Not Released row and trim 2.33 from the calendar

a6587bc

Matches what the calendar generators produce when mainline advances,
as the v2.38 rotation did by adding 2.39 Not Released and dropping
2.32.

Co-Authored-By: Claude Fable 5 <[email protected]>

denisra mentioned this pull request

Nov 4, 2026

docs: add the 2.40 Not Released row and trim 2.33 from the calendar #31750

Merged

denisra added a commit that referenced this pull request

Nov 4, 2026


          docs: add the 2.40 Not Released row and trim 2.33 from the calendar (#…

a9772b9

…31750)

Follow-up to #31715, which merged before this landed on its branch.
Applies the calendar rotation convention the docs-check bot flagged on
#31716: when mainline advances, append the next minor as Not Released
and trim the oldest Not Supported row, as the v2.38 rotation did with
2.39 and 2.32.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude  <[email protected]>

denisra merged commit 45569d3 into release/2.39

Nov 4, 2026

26 of 27 checks passed

Uh oh!

There was an error while loading. Please reload this page.

denisra deleted the docs-versions-239-backport branch

November 4, 2026 12:04

github-actions Bot locked and limited conversation to collaborators

Nov 4, 2026

Reviewers

nickvigilante

nickvigilante approved these changes

b-coder-b

Awaiting requested review from b-coder-b

+1 more reviewer

coderagents[bot]

coderagents[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Uh oh!

There was an error while loading. Please reload this page.

Assignees

denisra

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

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.

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.