chore(release): version packages - #231
Merged
Merged
Conversation
✅ Deploy Preview for openzeppelin-ui ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@openzeppelin/ui-dev-cli@1.4.0
Minor Changes
#229
4e7e728Thanks @pasevin! -check-peersnow warns when an adapter's declared@openzeppelin/ui-*range does not admitthe version installed beside it.
The check compared the minimum a range admits against the installed version, mirroring
validatePeerVersionsin@openzeppelin/ui-utils. That is right for the failure it wasbuilt for — an installed peer that is too old — but it left the opposite drift invisible: an
adapter declaring
^2.0.0against an installed4.0.1satisfies its own runtime check andstill cannot be installed by a consumer app, because a package manager reads the declared
range and not the baked minimum. Nothing anywhere reported it, which is how the
openzeppelin-adapterspackages carried v2 ranges forui-components,ui-reactandui-utilsacross two majors of the kit.Such pairs are now reported as a
warningwith codeoutdated-range, naming the bump thatfixes each one.
AdapterPeerPairgainsrange(the range as declared) andrangeSatisfied(whether the range itself admits the installed version, or
nullfor range syntax this checkdoes not model, which is left unreported rather than guessed at).
okand the exit coderemain driven by errors alone, so adding this to an existing pipeline does not change its
result;
printAdapterPeerResultprints warnings on the passing path, where they wouldotherwise be invisible.