Skip to content

docs: document patch release and backport policy - #31946

Closed
coder[bot] wants to merge 1 commit into
mainfrom
docs/releases-patch-backport-policy
Closed

coder[bot] wants to merge 1 commit into
mainfrom
docs/releases-patch-backport-policy

Conversation

@coder

@coder coder Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Adds a Patch releases and backports section to the Releases page. The page says mainline and stable receive "all bugfixes" but doesn't explain how patches reach each release:

  • Patch releases are unscheduled, and fixes land on main first.
  • A table of which fixes each channel receives, consistent with the existing channel descriptions and the cherry-pick / backport labels in CONTRIBUTING.md.
  • Bug-fix backports depend on severity and on how likely each release is to hit the bug; upgrading is the supported path otherwise.
  • Fixes that need a database schema change aren't backported and ship in the next minor.
  • How to request a patch release, plus a pointer to the preview image.

Pairs with the Support page change in DOCS-1731 ("contact Coder support" link).

Needs policy owner confirmation before merge

  • Who owns backport policy (Product or release management)?
  • The no-schema-changes-on-release-branches rule, as stated
  • The severity/likelihood framing for which releases get a bug fix
  • Whether there's a severity bar for an out-of-cycle patch worth publishing

Linear: DOCS-1732

@coder
coder Bot temporarily deployed to main November 9, 2026 23:37 Inactive
@coder
coder Bot temporarily deployed to main November 9, 2026 23:37 Inactive
@github-actions github-actions Bot added the community Pull Requests and issues created by the community. label Nov 9, 2026
@coder
coder Bot requested a review from nickvigilante November 9, 2026 23:37
@linear-code

linear-code Bot commented Nov 9, 2026

Copy link
Copy Markdown

DOCS-1732

@nickvigilante

Copy link
Copy Markdown
Collaborator

Closing and reopening under a human author, as required for this repository.

@nickvigilante
nickvigilante temporarily deployed to main November 10, 2026 15:55 — with GitHub Actions Inactive
@nickvigilante
nickvigilante temporarily deployed to main November 10, 2026 15:55 — with GitHub Actions Inactive
@nickvigilante
nickvigilante temporarily deployed to main November 10, 2026 15:55 — with GitHub Actions Inactive
@github-actions github-actions Bot locked and limited conversation to collaborators Nov 10, 2026
@nickvigilante
nickvigilante temporarily deployed to main November 10, 2026 15:55 — with GitHub Actions Inactive

This branch was previously deployed

1 inactive deployment
main — 7f13de58 Deployed Nov 10, 2026 by nickvigilante via cla #253493
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

community Pull Requests and issues created by the community.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant