@openzeppelin/[email protected]

Patch Changes

• Updated dependencies [83941c1]:
  • @openzeppelin/[email protected]
  • @openzeppelin/[email protected]

@openzeppelin/[email protected]

Minor Changes

• #55 83941c1 Thanks @pasevin! - Opt-in mainnet-L1 miss-fallback for forward+reverse ENS resolution (definitive-miss only, never-silent) with cross-network provenance triplet; requires @openzeppelin/ui-types ^3.3.0.

@openzeppelin/[email protected]

Patch Changes

• Updated dependencies [fd4f177, fd4f177, fd4f177, fd4f177]:
  • @openzeppelin/[email protected]
  • @openzeppelin/[email protected]
  • @openzeppelin/[email protected]
  • @openzeppelin/[email protected]
  • @openzeppelin/[email protected]

@openzeppelin/[email protected]

Patch Changes

• #50 fd4f177 Thanks @pasevin! - Raise the @openzeppelin/ui-types range floor from ^3.1.0 to ^3.2.0. The ENS v2 name-resolution work populates ResolutionProvenance.external and ResolutionProvenance.scopedToNetworkId, which were introduced in @openzeppelin/[email protected]; a consumer pinned to 3.1.0 would not have these fields on the shared provenance contract. No runtime change for workspace builds (the lockfile already resolves ui-types 3.2.0, which satisfies both the old and new floors).

@openzeppelin/[email protected]

Patch Changes

• #50 fd4f177 Thanks @pasevin! - Raise the @openzeppelin/ui-types range floor from ^3.1.0 to ^3.2.0. The ENS v2 name-resolution work populates ResolutionProvenance.external and ResolutionProvenance.scopedToNetworkId, which were introduced in @openzeppelin/[email protected]; a consumer pinned to 3.1.0 would not have these fields on the shared provenance contract. No runtime change for workspace builds (the lockfile already resolves ui-types 3.2.0, which satisfies both the old and new floors).

@openzeppelin/[email protected]

Patch Changes

• #50 fd4f177 Thanks @pasevin! - Raise the @openzeppelin/ui-types range floor from ^3.1.0 to ^3.2.0. The ENS v2 name-resolution work populates ResolutionProvenance.external and ResolutionProvenance.scopedToNetworkId, which were introduced in @openzeppelin/[email protected]; a consumer pinned to 3.1.0 would not have these fields on the shared provenance contract. No runtime change for workspace builds (the lockfile already resolves ui-types 3.2.0, which satisfies both the old and new floors).

• #50 fd4f177 Thanks @pasevin! - Raise every declared viem range floor to ^2.35.0 — the minimum version the official ENS v2 readiness guide requires. viem 2.35.0 is where the new DAO-owned Universal Resolver proxy (0xeeee…eeee) landed in the chain definitions; the old floors (^2.28.0 peer, ^2.33.3 dependency) let a consumer-pinned viem resolve ENS names through the pre-v2 Universal Resolver, which breaks as ENS v2 rolls out. No runtime change for workspace builds (the lockfile already resolves viem 2.44.4, which satisfies the new floor).

@openzeppelin/[email protected]

Patch Changes

• #50 fd4f177 Thanks @pasevin! - Raise the @openzeppelin/ui-types range floor from ^3.1.0 to ^3.2.0. The ENS v2 name-resolution work populates ResolutionProvenance.external and ResolutionProvenance.scopedToNetworkId, which were introduced in @openzeppelin/[email protected]; a consumer pinned to 3.1.0 would not have these fields on the shared provenance contract. No runtime change for workspace builds (the lockfile already resolves ui-types 3.2.0, which satisfies both the old and new floors).

@openzeppelin/[email protected]

Minor Changes

• #50 fd4f177 Thanks @pasevin! - Wire the ENS name-resolution capability into the EVM runtime profiles, injecting the L1 public client the capability requires (the nameResolution factory plus the optional ensL1Client for ENS v2 cross-chain resolution).

  Hardening: the L1 mainnet ENS RPC (for the ENS v2 cross-chain path) resolves via user → override → viem-default keyed on the mainnet id, so operators can supply a keyed endpoint; no secret is hardcoded.

Patch Changes

• #50 fd4f177 Thanks @pasevin! - Raise the @openzeppelin/ui-types range floor from ^3.1.0 to ^3.2.0. The ENS v2 name-resolution work populates ResolutionProvenance.external and ResolutionProvenance.scopedToNetworkId, which were introduced in @openzeppelin/[email protected]; a consumer pinned to 3.1.0 would not have these fields on the shared provenance contract. No runtime change for workspace builds (the lockfile already resolves ui-types 3.2.0, which satisfies both the old and new floors).

• #50 fd4f177 Thanks @pasevin! - Raise every declared viem range floor to ^2.35.0 — the minimum version the official ENS v2 readiness guide requires. viem 2.35.0 is where the new DAO-owned Universal Resolver proxy (0xeeee…eeee) landed in the chain definitions; the old floors (^2.28.0 peer, ^2.33.3 dependency) let a consumer-pinned viem resolve ENS names through the pre-v2 Universal Resolver, which breaks as ENS v2 rolls out. No runtime change for workspace builds (the lockfile already resolves viem 2.44.4, which satisfies the new floor).

• #50 fd4f177 Thanks @pasevin! - Switch the default ethereum-mainnet RPC to a keyless, CORS-friendly public endpoint (https://ethereum-rpc.publicnode.com) instead of relying on viem's default mainnet transport, which is not a dependable browser default (CORS). Verified live (eth_chainId → 0x1) with a browser preflight returning access-control-allow-origin: * and POST allowed. This default also serves as the last-resort fallback for the ENS v2 L1 cross-chain path (resolveMainnetRpcUrl), so both browser mainnet resolution and cross-chain ENS get a CORS-safe default. No behavior change for consumers that supply their own RPC via user config or app-config override.

@openzeppelin/[email protected]

Patch Changes

• #48 712a007 Thanks @pasevin! - chore(deps): resolve remaining Dependabot security alerts for transitive dependencies

  Update the workspace pnpm overrides so vulnerable transitive dependencies resolve to patched versions:

  • protobufjs → ^7.6.3 (was pinned to ^7.5.8, still allowed 7.6.x advisories)
  • hono → ^4.12.25 (was ^4.12.21)
  • ws → ^8.21.0 for the v8 line and ^7.5.11 for the v7 line
  • form-data → ^4.0.6 (CRLF injection)
  • ua-parser-js → ^2.0.10 (ReDoS)
  • js-yaml (v4) → ^4.2.0 (quadratic-complexity DoS)
  • uuid → ^11.1.1 (missing buffer bounds check)
  • @babel/core → ^7.29.6 (arbitrary file read via sourceMappingURL)

  elliptic (<= 6.6.1) has no published fix and remains; it is a low-severity advisory with no upstream patch available.

  These overrides only affect dependency resolution within this monorepo's lockfile and do not change the published packages' declared dependency ranges.

• Updated dependencies [712a007]:

  • @openzeppelin/[email protected]
  • @openzeppelin/[email protected]
  • @openzeppelin/[email protected]
  • @openzeppelin/[email protected]
  • @openzeppelin/[email protected]

@openzeppelin/[email protected]

Patch Changes

• #48 712a007 Thanks @pasevin! - chore(deps): resolve remaining Dependabot security alerts for transitive dependencies

  Update the workspace pnpm overrides so vulnerable transitive dependencies resolve to patched versions:

  • protobufjs → ^7.6.3 (was pinned to ^7.5.8, still allowed 7.6.x advisories)
  • hono → ^4.12.25 (was ^4.12.21)
  • ws → ^8.21.0 for the v8 line and ^7.5.11 for the v7 line
  • form-data → ^4.0.6 (CRLF injection)
  • ua-parser-js → ^2.0.10 (ReDoS)
  • js-yaml (v4) → ^4.2.0 (quadratic-complexity DoS)
  • uuid → ^11.1.1 (missing buffer bounds check)
  • @babel/core → ^7.29.6 (arbitrary file read via sourceMappingURL)

  elliptic (<= 6.6.1) has no published fix and remains; it is a low-severity advisory with no upstream patch available.

  These overrides only affect dependency resolution within this monorepo's lockfile and do not change the published packages' declared dependency ranges.