Overview

As we update our release channels to support stable and mainline, we will also improve how we communicate best installation practices to customers. Our install.sh script will support a --stable flag, but automating this for external package managers (Helm, Brew, Winget) would require much greater effort.

In reality, the best practice installing coder via these package managers is to explicitly specify the desired version every install. To encourage customers to adopt this habit, we will add automation to insert the latest version tags (stable and mainline) into the docs like so:

To enforce this, we'll open the page with a disclaimer on the Helm page (a high-volume installation path):

Requirements

Dynamic (Required)

• Release script adds version flags with mainline+stable releases to helm install docs (pictured)

Dynamic (Nice-to-have)

Not necessary at all, depends on required effort

• Release script adds version flags with mainline+stable releases to brew install docs
• `` Winget install docs
• `` System Packages install docs

Static (Required)

• Add Helm disclaimer on versioning
• Brew version advisor
• Winget version advisor
• Other "System Packages" advisor
• install.sh mentions --stable flag