docs(roadmap): record v2.12 and correct the current-version line - #20
Merged
Conversation
The current-version line still read v2.11.0 after the version moved to 2.12.0, and the overrides work had no ROADMAP entry while v2.10 and v2.11 both do. Surfaced by the PR #19 review as a non-blocking note; the drift is real, so it is corrected here rather than left. English SSoT and Korean mirror together.
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.
Docs-only follow-up to #19.
Problem
package.jsonmoved to2.12.0in #19, butROADMAP.md/ROADMAP.ko.mdstill saidcurrent: v2.11.0, and the npmoverrideswork had no ROADMAP entry even though v2.10 and v2.11 both do.The PR #19 review flagged this as non-blocking and out-of-criteria. It is still real drift against this repo's own version-SSoT convention, so it is corrected rather than left behind.
Change
v2.11.0→v2.12.0in both the English SSoT and the Korean mirror## v2.12section in both, matching how v2.10 and v2.11 are written: what the feature fixes, the approval scoping, and the verification that backs itNo code changes, so no version bump.
Verification
npm testgreengit diff --checkclean