Skip to content

Prove the PrimeReact 11 adapter against PrimeReact 11.2.0 - #378

Merged
woksin merged 1 commit into
mainfrom
fix/primereact-112-boundary
Sep 29, 2026
Merged

woksin merged 1 commit into
mainfrom
fix/primereact-112-boundary

Conversation

@woksin

@woksin woksin commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

The PrimeReact 11 adapter is now proven against PrimeReact 11.2.0, the release that renamed @primereact/styles/password and broke Components 3.6.1. The 4.x adapter imports none of the renamed subpaths. This PR publishes nothing; the updated notices and compatibility evidence ship with the next release.

Changed

The Components 3.x fix for #375 needs a maintenance release path and is tracked on the issue.

PrimeReact 11.2.0 renamed @primereact/styles/password to inputpassword,
which breaks Components 3.6.1 (#375). The 4.x adapter imports none of the
renamed subpaths: its current boundary now installs 11.2.0 and passes the
packed consumer check with npm, pnpm and Yarn PnP, and the compatibility
manifests record the new verified peers. The license text is unchanged from
11.1.0. The README and notices name the proven versions.
@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 ae9048e into main Sep 29, 2026
53 of 54 checks passed
@woksin
woksin deleted the fix/primereact-112-boundary branch September 29, 2026 16:59
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