chore(release): version packages - #218
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.2.0
Minor Changes
#217
4a363a6Thanks @pasevin! - Addoz-ui-dev check-peers, a static guard for stale@openzeppelin/ui-*pins.@openzeppelin/adapter-*packages declare peerDependencies on@openzeppelin/ui-*butenforce them only at runtime, inside
validatePeerVersions(). A repository that bumps theadapters to a new major without moving its
ui-*pins passes typecheck, tests, build andlint, and then fails in the browser with the network runtime stuck in a failed state. There
was nothing to catch it before the app was loaded.
The command follows the same contract as
doctor:-p, --projectdefaults to the currentworking directory,
--jsonemits a machine-readable result with anokboolean and anissuesarray, and the process exits1on failure.Workspace resolution reuses
collectWorkspacePackageDirs, so it scansnode_modules/@openzeppelinat the repository root and next to every workspace packagedeclared in
pnpm-workspace.yaml. That covers repositories whose dependencies are hoisted tothe root as well as those that install under an app, and it means an app resolving an older
peer than its siblings is reported rather than hidden behind a hoisted copy.
Comparison semantics mirror
validatePeerVersions: each adapter bakes its peer minimums atbuild time as
range.replace(/^\^/, ''), so the check compares the installed version againstthe minimum the range admits, not the range itself.
ui-utils4.0.0 against a declared^2.0.0passes, because the adapter only asks for>=2.0.0.Failure output names the workspace
package.jsonfiles that declare the ranges, keeps thewarning that a caret alone may not move the install (
^3.3.0already permits 3.5.1, so astale lockfile entry stays stale until re-resolved), and mentions
pnpm-workspace.yamloverrides only when the repository actually pins
@openzeppelin/ui-*there.Nothing-to-check states — no
@openzeppelinpackages, no adapters installed, no peersresolved — are failures rather than a silent pass, since in CI they mean the install did not
run or
--projectpoints at the wrong root.This is a separate command from
doctorby design.doctorvalidates the local-developmentworkflow (families, repo roots, packed manifests) and is expected to report issues in CI,
where local development is off; this guard has to pass there.