Skip to content

Document Components 3 with PrimeReact 11.2 and guard 3.x releases on main - #380

Merged
woksin merged 4 commits into
mainfrom
docs/components3-primereact-112
Sep 29, 2026
Merged

woksin merged 4 commits into
mainfrom
docs/components3-primereact-112

Conversation

@woksin

@woksin woksin commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

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

Troubleshooting explains the Components 3 build failure with PrimeReact
11.2 and its remedies (#375). release.md describes publishing 3.x
maintenance releases from support/3.x under the v3-lts dist-tag (#379)
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)
…he docs

The older-major guard checks the version format before any arithmetic, so a
crafted input cannot run as a command, and fails if the current major cannot
be read. release.md says main refuses an older major, and troubleshooting
names the 3.x versions that accept PrimeReact 11.2 (#375, #379)
@woksin woksin added the no-release Merging publishes no package, image, release, or deployment label Sep 29, 2026
@woksin woksin self-assigned this Sep 29, 2026
@woksin
woksin merged commit 16cb9ad into main Sep 29, 2026
53 of 54 checks passed
@woksin
woksin deleted the docs/components3-primereact-112 branch September 29, 2026 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-release Merging publishes no package, image, release, or deployment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant