Coder powers secure, scalable development across key industries — automotive, finance, government, and technology — enabling faster builds, tighter compliance, and seamless AI adoption in enterprise-grade cloud environments.
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 primary release channels, as well as ad-hoc release candidates:
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
Release Candidates: Ad-hoc builds to validate in-development features
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
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.34.
Ad-hoc builds that Coder releases to validate in-development features with select customers
Not guaranteed to be stable or free of bugs
Features introduced in an RC are not guaranteed to be included in a mainline or stable release
Not intended for production use
Release candidates give Coder a way to push out builds for customers and other users to try out new, under-development functionality without cutting a new minor version. Unlike mainline and stable releases, RCs do not follow a fixed schedule and carry no guarantees around stability or long-term support. They exist purely as a feedback mechanism: Coder can ship targeted builds, gather real-world input, and iterate before committing changes to the standard release channels.
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.
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.
