Skip to content

docs: point release docs at the Tag release workflow - #31459

Closed
f0ssel wants to merge 5 commits into
f0ssel/releaser-tag-release-workflowfrom
f0ssel/release-yaml-tag-release-dispatch
Closed

f0ssel wants to merge 5 commits into
f0ssel/releaser-tag-release-workflowfrom
f0ssel/release-yaml-tag-release-dispatch

Conversation

@f0ssel

@f0ssel f0ssel commented Oct 28, 2026 •

Copy link
Copy Markdown
Member

Points the Releases section of CONTRIBUTING.md at the Tag release workflow from #31321. Stacked on #31321.

The section previously described release.yaml inputs that no longer exist. It now covers cutting a release or patch with Tag release (dry run first), the allow_open_prs and allow_breaking_changes overrides, and retrying a failed run. It says to run ./scripts/release.sh manually only for RCs on main, checks without a workflow override, or editing notes before tagging.

Merge after #31321 is on the release branches people will release from, so the docs don't point at a workflow that isn't there yet.

pnpm check-docs passes.


Generated by Coder Agents on behalf of @f0ssel.

Allow the release App in check-perms, record the requesting user from
Tag release, and point the release docs at the Tag release workflow.
Drop the requested_by inputs and the releaser code that sent them.
@f0ssel f0ssel changed the title feat: accept Tag release dispatches in release.yaml docs: point release docs at the Tag release workflow Oct 28, 2026
@linear-code

linear-code Bot commented Nov 10, 2026

Copy link
Copy Markdown

CODAGT-1549

This branch had an error being deployed

1 failed deployment
docs-preview — 4f7ba1fa Deployed Nov 16, 2026 by f0ssel via cleanup #128
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant