mirror of https://github.com/coder/coder.git synced 2026-06-04 13:38:21 +00:00

Files

T

blinkagent[bot] 3704e930a1 docs: update release calendar for v2.31 (#23113 )

The release calendar was outdated — it still showed v2.30 as Mainline
and v2.31 as Not Released.

This runs the `scripts/update-release-calendar.sh` script and manually
re-adds the ESR rows that the script doesn't handle:

**Changes:**
- v2.28: Security Support → Not Supported
- v2.29: Stable + ESR → Security Support + ESR (v2.29.8)
- v2.30: Mainline → Stable (v2.30.3)
- v2.31: Not Released → Mainline (v2.31.5)
- Added 2.32 as Not Released
- Kept 2.24 as Extended Support Release
- Updated latest patch versions for all releases
- Removed 2.25 (no longer in the rolling window)

Created on behalf of @matifali

Co-authored-by: blink-so[bot] <211532188+blink-so[bot]@users.noreply.github.com>

2026-03-16 14:20:39 +00:00

5.0 KiB

Raw Blame History

Releases

Coder releases are cut directly from main in our GitHub on the first Tuesday of each month.

We recommend enterprise customers test the compatibility of new releases with their infrastructure on a staging environment before upgrading a production deployment.

Release channels

We support four release channels:

Mainline: The bleeding edge version of Coder
Stable: N-1 of the mainline release
Security Support: N-2 of the mainline release
Extended Support Release: Biannually released version of Coder

We field our mainline releases publicly for one month before promoting them to stable. The security support version, so n-2 from mainline, receives patches only for security issues or CVEs.

Mainline releases

Intended for customers with a staging environment
Gives earliest access to new features
May include minor bugs
All bugfixes and security patches are supported

Stable releases

Safest upgrade/installation path
May not include the latest features
All bugfixes and security patches are supported

Security Support

In-product security vulnerabilities and CVEs are supported

For more information on feature rollout, see our feature stages documentation.

Extended Support Release

Designed for organizations that prioritize long-term stability
Receives only critical bugfixes and security patches
Ideal for regulated environments or large deployments with strict upgrade cycles

ESR releases will be updated with critical bugfixes and security patches that are available to paying customers. This extended support model provides predictable, long-term maintenance for organizations that require enhanced stability. Because ESR forgoes new features in favor of maintenance and stability, it is best suited for teams with strict upgrade constraints. The latest ESR version is Coder 2.29.

For more information, see the Coder ESR announcement or our ESR Upgrade Guide.

Installing stable

When installing Coder, we generally advise specifying the desired version from our GitHub releases page.

You can also use our install.sh script with the stable flag to install the latest stable release:

curl -fsSL https://coder.com/install.sh | sh -s -- --stable

Best practices for installing Coder can be found on our install pages.

Release schedule

Release name	Release Date	Status	Latest Release
2.24	July 01, 2025	Extended Support Release	v2.24.4
2.26	September 03, 2025	Not Supported	v2.26.6
2.27	October 02, 2025	Not Supported	v2.27.11
2.28	November 04, 2025	Not Supported	v2.28.11
2.29	December 02, 2025	Security Support + ESR	v2.29.8
2.30	February 03, 2026	Stable	v2.30.3
2.31	February 23, 2026	Mainline	v2.31.5
2.32		Not Released	N/A

Tip

We publish a preview image ghcr.io/coder/coder-preview on each commit to the main branch. This can be used to test under-development features and bug fixes that have not yet been released to mainline or stable.

The preview image is not intended for production use.

January Releases

Releases on the first Tuesday of January are not guaranteed to occur because most of our team is out for the December holiday period. That being said, an ad-hoc release might still occur. We advise not relying on a January release, or reaching out to Coder directly to determine if one will be occurring closer to the release date.

5.0 KiB Raw Blame History