Prove the PrimeReact 11 adapter against PrimeReact 11.2.0 - #378
Merged
Merged
Conversation
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.
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.
The PrimeReact 11 adapter is now proven against PrimeReact 11.2.0, the release that renamed
@primereact/styles/passwordand 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.