fix: correct duplicate v19.2.1 entry to v19.2.2 on Versions page#8476
Open
Ashutosh0x wants to merge 1 commit into
Open
fix: correct duplicate v19.2.1 entry to v19.2.2 on Versions page#8476Ashutosh0x wants to merge 1 commit into
Ashutosh0x wants to merge 1 commit into
Conversation
Fixes reactjs#8429 The first v19.2.1 entry links to CHANGELOG anchor reactjs#1922 (v19.2.2, Dec 11) but was mislabeled as v19.2.1. The second entry correctly links to reactjs#1921 (v19.2.1, Dec 3). This matches the pattern of v19.1.3/v19.1.2 and v19.0.2/v19.0.1.
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
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
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.
Summary
Fixes duplicate v19.2.1 entry on the React Versions page.
Closes #8429
Problem
The Versions page lists
v19.2.1twice with different CHANGELOG anchors:v19.2.1linking to#1922-dec-11-2025v19.2.1linking to#1921-dec-3-2025Fix
The first entry's anchor
#1922corresponds to v19.2.2 (December 11, 2025), not v19.2.1. This matches the pattern across all version lines:Changed the first entry from
v19.2.1tov19.2.2.cc @rickhanlonii