Document Components 3 with PrimeReact 11.2 and guard 3.x releases on main - #380
Merged
Merged
Conversation
Name the exact dispatch command and the danger of dispatching on main, explain that re-runs continue a partial publish, correct why 3.x creates no GitHub release, and add the manual tag recovery (#379)
A 3.x version dispatched on main would create its GitHub release there. Older majors are released from their support branch (#379)
This was referenced Sep 29, 2026
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.
Components 3 users hitting the PrimeReact 11.2 build failure now find the cause and the remedy, and maintainers have a documented, safe path for 3.x maintenance releases. This PR publishes nothing.
Changed
release.mddescribes how to release Components 3 maintenance versions fromsupport/3.xunder thev3-ltsdist-tag, and how to recover if a run stops partway or a dist-tag goes wrong. See Add a safe release path for Components 3.x maintenance fixes #379.mainby mistake. It checks the version's format before comparing it. See Add a safe release path for Components 3.x maintenance fixes #379.