From f04b8165f3349265c868dfa412b0277eb7bd0476 Mon Sep 17 00:00:00 2001 From: "oz-release-app[bot]" <205211949+oz-release-app[bot]@users.noreply.github.com> Date: Wed, 9 Sep 2026 12:43:15 +0000 Subject: [PATCH] chore(release): version packages --- .changeset/check-peers-outdated-range.md | 23 ----------------------- packages/dev-cli/CHANGELOG.md | 24 ++++++++++++++++++++++++ packages/dev-cli/package.json | 2 +- 3 files changed, 25 insertions(+), 24 deletions(-) delete mode 100644 .changeset/check-peers-outdated-range.md diff --git a/.changeset/check-peers-outdated-range.md b/.changeset/check-peers-outdated-range.md deleted file mode 100644 index def053f2..00000000 --- a/.changeset/check-peers-outdated-range.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -'@openzeppelin/ui-dev-cli': minor ---- - -`check-peers` now warns when an adapter's declared `@openzeppelin/ui-*` range does not admit -the version installed beside it. - -The check compared the *minimum* a range admits against the installed version, mirroring -`validatePeerVersions` in `@openzeppelin/ui-utils`. That is right for the failure it was -built for — an installed peer that is too old — but it left the opposite drift invisible: an -adapter declaring `^2.0.0` against an installed `4.0.1` satisfies its own runtime check and -still 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-adapters` packages carried v2 ranges for `ui-components`, `ui-react` and -`ui-utils` across two majors of the kit. - -Such pairs are now reported as a `warning` with code `outdated-range`, naming the bump that -fixes each one. `AdapterPeerPair` gains `range` (the range as declared) and `rangeSatisfied` -(whether the range itself admits the installed version, or `null` for range syntax this check -does not model, which is left unreported rather than guessed at). `ok` and the exit code -remain driven by errors alone, so adding this to an existing pipeline does not change its -result; `printAdapterPeerResult` prints warnings on the passing path, where they would -otherwise be invisible. diff --git a/packages/dev-cli/CHANGELOG.md b/packages/dev-cli/CHANGELOG.md index c3b490cf..da54724e 100644 --- a/packages/dev-cli/CHANGELOG.md +++ b/packages/dev-cli/CHANGELOG.md @@ -1,5 +1,29 @@ # @openzeppelin/ui-dev-cli +## 1.4.0 + +### Minor Changes + +- [#229](https://github.com/OpenZeppelin/openzeppelin-ui/pull/229) [`4e7e728`](https://github.com/OpenZeppelin/openzeppelin-ui/commit/4e7e7280bb62f64e107c181dbcb26e29521e18bf) Thanks [@pasevin](https://github.com/pasevin)! - `check-peers` now warns when an adapter's declared `@openzeppelin/ui-*` range does not admit + the version installed beside it. + + The check compared the _minimum_ a range admits against the installed version, mirroring + `validatePeerVersions` in `@openzeppelin/ui-utils`. That is right for the failure it was + built for — an installed peer that is too old — but it left the opposite drift invisible: an + adapter declaring `^2.0.0` against an installed `4.0.1` satisfies its own runtime check and + still 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-adapters` packages carried v2 ranges for `ui-components`, `ui-react` and + `ui-utils` across two majors of the kit. + + Such pairs are now reported as a `warning` with code `outdated-range`, naming the bump that + fixes each one. `AdapterPeerPair` gains `range` (the range as declared) and `rangeSatisfied` + (whether the range itself admits the installed version, or `null` for range syntax this check + does not model, which is left unreported rather than guessed at). `ok` and the exit code + remain driven by errors alone, so adding this to an existing pipeline does not change its + result; `printAdapterPeerResult` prints warnings on the passing path, where they would + otherwise be invisible. + ## 1.3.0 ### Minor Changes diff --git a/packages/dev-cli/package.json b/packages/dev-cli/package.json index 28ea78ce..7b855618 100644 --- a/packages/dev-cli/package.json +++ b/packages/dev-cli/package.json @@ -1,7 +1,7 @@ { "name": "@openzeppelin/ui-dev-cli", "private": false, - "version": "1.3.0", + "version": "1.4.0", "description": "Shared local development CLI for OpenZeppelin UI consumer applications.", "type": "module", "bin": {