Part ofStable Releases.

Overview

We need to extend the capability of our release script now that we differentiate stable and mainline releases. This means the release script can intelligently publish each type by accepting a flag (--stable).

Requirements

Publishing a mainline release (no flag):

Used for the tip of our releases, monthly.

• Cuts a release from main
• Skipslatest github label (now used to identifystable)
• Adds a disclaimer in just before the changelog (example mock here):

• The "latest stable release" link points tocoder/coder/releases/latest

• The "documentation" link points to a newdocs/install/releases page

• updates the install.sh script with the latest mainline version (this version)
  CODER_MAINLINE_VERSION=v2.9.0

Publishing a stable patch (--stable flag):

Used to patch security issues, regressions onstable

• Cuts cherry-picked patch to stable
• Includeslatest Github label
• Appends "(Stable)" text to release name (see mockup)

Need engineering input on how this works with Github automation, or if it needs to be manually triggered.