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.

We support two release channels: mainline for the bleeding edge version of Coder and stable for those with lower tolerance for fault. We field our mainline releases publicly for one month before promoting them to stable. The version prior to stable 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.

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

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.

Important: The preview image is not intended for production use.