You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore(release): replace semver-major exclusion with only-land-on-next label (#8660)
semver-major commits are now cherry-picked into stable release proposals
(treated as patches, gated behind a flag) but excluded from release notes.
The new `only-land-on-next` label replaces the old per-version
`dont-land-on-vN.x` labels to mark commits that should only land on the
next major release line (master) and not on any current stable line.
Co-authored-by: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,9 +71,9 @@ In the event that some existing functionality _does_ need to change, as much as
71
71
72
72
## Indicate intended release targets
73
73
74
-
When writing major changes we use a series of labels in the form of `dont-land-on-vN.x` where N is the major release line which a PR should not land in. Every PR marked as semver-major should include these tags. These tags allow our [branch-diff](https://github.com/bengl/branch-diff) tooling to work smoothly as we can exclude PRs not intended for the release line we're preparing a release proposal for. The `semver-major` labels on their own are not sufficient as they don't encode any indication of from _which_ releases they are a major change.
74
+
When writing changes that should only land on the next major release line (master) and not on any current stable release line, add the `only-land-on-next` label. This tells our [branch-diff](https://github.com/bengl/branch-diff) tooling to exclude those PRs when preparing a release proposal for a stable line.
75
75
76
-
For outside contributions we will have the relevant team add these labels when they review and determine when they plan to release it.
76
+
For outside contributions we will have the relevant team add this label when they review and determine the intended release target.
0 commit comments