Skip to content

Describe releases from stable branches in the agent docs - #9171

Open
craigmichaelmartin wants to merge 1 commit into
mainfrom
release-docs-stable-flow
Open

craigmichaelmartin wants to merge 1 commit into
mainfrom
release-docs-stable-flow

Conversation

@craigmichaelmartin

Copy link
Copy Markdown
Contributor

WHY are these changes introduced?

Releases now ship from stable/X.Y branches (#9165), but the agent docs still described a version bump on main and a stable/X.Y branch created from the release tag afterwards.

WHAT is this pull request doing?

  • AGENTS.md:
    • The Releases section describes the stable-branch flow: a Dev Experience member cuts stable/X.Y at a green main commit.
    • The Version Packages pull request is closed and reopened so its checks run, and its head is tested and merged with a merge commit pinned to it.
    • Only the release owner merges into the branch during a release.
  • TORRENT_WORKFLOW.md: pull requests to stable/X.Y are for patch backports, and only the release owner merges during an open release.
  • write_release_descriptions:
    • It takes a "Version Packages - stable/X.Y" pull request, for a minor or a patch.
    • It finds each change's pull request from its changeset file.
    • It notes that the release workflow creates the GitHub release itself.

How to manually test your changes?

Read the three files against .github/workflows/release.yml.

🤖 Generated with Claude Code

AGENTS.md, TORRENT_WORKFLOW.md and the write_release_descriptions command now say that minor and
patch releases ship from stable/X.Y: a Dev Experience member cuts the branch at a green main
commit, the Version Packages pull request's head is tested and merged with a merge commit pinned
to it, and main doesn't publish releases.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@craigmichaelmartin
craigmichaelmartin requested a review from a team as a code owner November 18, 2026 18:46
@github-actions github-actions Bot added the no-changelog This PR doesn't include a changeset entry. Is an internal only change not relevant to end users. label Nov 18, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-changelog This PR doesn't include a changeset entry. Is an internal only change not relevant to end users.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants