docs: correct edge version shape to the as-built NB.GV form - #319
Merged
Conversation
Edge actually publishes 2026.1.0-edge.<height>.g<commit> (NB.GV-native height + commit, main being a non-public ref), not the date-stamped 2026.x-edge.<YYYYMMDD> form the docs illustrated. Aligns AGENTS.md, branching-and-release.md, and release-and-versioning.md to reality, and adds a dated implementation note to ADR-0004 (decision intent preserved; example corrected) plus points the edge prose at the now-shipped .github/workflows/edge.yml. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ChrisonSimtian
added
documentation
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.
Resolves the doc-vs-reality mismatch flagged during the rollout: edge actually publishes
2026.1.0-edge.<height>.g<commit>(NB.GV-native height + commit, sincemainis a non-public ref), not the date-stamped2026.x-edge.<YYYYMMDD>form the docs illustrated. Per maintainer decision, we keep the shipping form and align the docs to it (the commit identifier is more precise than a date and NB.GV produces it natively).AGENTS.md,docs/branching-and-release.md,docs/agents/release-and-versioning.md— edge-version examples corrected to the real shape; edge prose now points at the shipped.github/workflows/edge.yml.docs/adr/0004-…— decision intent preserved (identifier in the prerelease segment, not the core); added a dated implementation note recording the as-built string and that a literal date stamp was not implemented. Did not rewrite the decision.🤖 Generated with Claude Code