Part of Stable Releases.

Overview

We're bisecting our releases into two channels: "stable" and "mainline."

• mainline: points to true latest release
• stable: points to latest release that's been fielded for at least 2 weeks

By default, our install.sh script will point to the mainline release, similar to the current behavior. Additionally, users can specify a --stable flag to use the latest release marked stable.

This allows customers/community members either: continue using install.sh as is and always get the latest version of Coder, or safely install the release that's behind, but stable.

The way we've discussed doing this is by putting a variable in install.sh like

CODER_MAINLINE_VERSION=v2.9.0

Since the coder/coder/releases/latest will always find the release with the latest tag, which will always be the latest stable release.

Example usage (2.9.1=mainline, 2.8.4=stable):

• Install mainline:
  curl -fsSL https://coder.com/install.sh | sh → 2.9.1
• Install stable:
  curl -fsSL https://coder.com/install.sh | sh -s -- --stable → 2.8.4

Requirements

• install script stores latest mainline release version
  CODER_MAINLINE_VERSION=v2.9.0

• --stable makes install script point to the latest release in Github
  https://github.com/coder/coder/releases/latest

• Default usage now points to mainline (previously called "edge")

• Introduces a new version advisory message:

  When installing mainline:

  Coder mainline release v2.9.0 installed. To install our stable release (v2.8.3), use the --stable flag. See our releases documentation or Github for more information on versioning.

  When installing stable:

  Coder stable release v2.8.3 installed. See our releases documentation or Github for more information on versioning.

  Would be nice to have a link to the new releases page in the docs in that advisory.