Align docs on evergreen target/vCurrent + target/vNext labels - #485
Merged
Conversation
ChrisonSimtian
added
documentation
AGENTS.md and the versioning docs prescribed year-based target/YYYY labels (per ADR-0004), but the repo actually standardised on evergreen target/vCurrent / target/vNext. Reconcile the docs to the real labels: - AGENTS.md rule #1, CONTRIBUTING.md, release-and-versioning.md (targeting section + PR-creation flow), issue-and-pr-style.md, .github/release.yml comments, and the story-writer + new-issue commands now reference target/vCurrent / target/vNext. - ADR-0004's label-migration line marked superseded (2026-07-13) rather than rewritten, preserving the decision record. Legacy maintenance work still uses target/v10. Docs-only, non-breaking. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ChrisonSimtian
force-pushed
the
docs/evergreen-target-labels
branch
from
July 13, 2026 01:57
9b11716 to
f0f6c19
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The docs prescribed year-based
target/YYYYlabels (target/2026), but the repo actually uses evergreentarget/vCurrent/target/vNext. This reconciles the docs to reality — no GitHub label changes, no PR relabeling.story-writer/new-issuecommand docs now saytarget/vCurrent(current line) /target/vNext(next year's major).Legacy maintenance work still uses
target/v10. Docs-only, non-breaking.