Skip to content

Make major release decisions maintainer-owned and explicit #396

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rmcdaniel merged 1 commit into from
Nov 13, 2026
+5 −3
Merged

Make major release decisions maintainer-owned and explicit #396

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -274,9 +274,11 @@ approval workflow or aesthetic restrictions.
- Each package repository owns ordinary semantic-version releases and
publication through a small repository-local workflow. Sample App, Cloud,
and the documentation site do not publish versioned packages.
- A major release issue states the proposed versions, checks, conformance links,
and human decision. Patch and minor releases follow repository policy and
semantic versioning without a central cross-repository release controller.
- A major release issue records the proposed versions, migration and rollback
impact, required checks and conformance links, and the responsible maintainer's
release decision. Honor any approval explicitly reserved for that release.
Patch and minor releases follow repository policy and semantic versioning
without a central cross-repository release controller.

### Cross-Repository Release Follow-Through

Expand Down
Loading