chore(deps): update dependency zod to ^3.22.0 || ^4.4.3 - #30
chore(deps): update dependency zod to ^3.22.0 || ^4.4.3#30renovate[bot] wants to merge 1 commit into
Conversation
|
PR author is in the excluded authors list. |
|
4006ecd to
6a5746f
Compare
6a5746f to
07b7c38
Compare
07b7c38 to
1de4b54
Compare
0fa8173 to
3623ebe
Compare
3623ebe to
25f6b82
Compare
| "peerDependencies": { | ||
| "@opentelemetry/api": "^1.7.0", | ||
| "zod": "^3.22.0" | ||
| "zod": "^3.22.0 || ^4.4.3" |
There was a problem hiding this comment.
🟡 Changelog not updated for a user-facing dependency change
The supported version range for a required companion library is widened ("zod": "^3.22.0 || ^4.4.3" at package.json:286) without adding a matching entry under the Unreleased section of CHANGELOG.md, so consumers get no record of the change.
Impact: Users reading the changelog won't learn that a newer major version of the required companion library is now supported.
Repository rule: changelog must be updated for user-facing changes
AGENTS.md states: "Conventional Commit titles; update CHANGELOG.md (Unreleased) for user-facing changes." A peer dependency range widening is user-facing (it changes install-time compatibility), but CHANGELOG.md still has an empty ## [Unreleased] section (CHANGELOG.md:7).
Prompt for agents
AGENTS.md requires updating CHANGELOG.md under the Unreleased heading for user-facing changes. This PR widens the zod peer dependency range in package.json but CHANGELOG.md's Unreleased section is empty. Add a Changed entry noting that zod 4.x (>=4.4.3) is now an accepted peer dependency alongside zod 3.x.
Was this helpful? React with 👍 or 👎 to provide feedback.
| "peerDependencies": { | ||
| "@opentelemetry/api": "^1.7.0", | ||
| "zod": "^3.22.0" | ||
| "zod": "^3.22.0 || ^4.4.3" |
There was a problem hiding this comment.
🔍 zod peer dependency is declared but never imported in src
Grepping the repo shows no zod import anywhere in src/ — it only appears in package.json, the lockfile, README, and .wave/repo.json. Widening the range is therefore risk-free at runtime, but it also raises the question of whether zod should be a (non-optional) peer dependency at all, since consumers are forced to install it even though the SDK never uses it.
Was this helpful? React with 👍 or 👎 to provide feedback.
25f6b82 to
335d04c
Compare
ApprovabilityVerdict: Needs human review Unable to check for correctness in 335d04c. This peer dependency version widening is low-risk, but the changed files are owned by wave-av/core-team and should be reviewed by a designated owner. An unresolved comment also notes a missing CHANGELOG entry per repo conventions. No code changes detected at You can customize Macroscope's approvability policy. Learn more. |
335d04c to
2738bb7
Compare


This PR contains the following updates:
^3.22.0→^3.22.0 || ^4.4.3Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.
Note
Widen
zoddependency range to accept v3.22.x or v4.4.3+Updates package.json to accept
zod^3.22.0 || ^4.4.3, allowing either the v3 or v4 major to be resolved during installation.Macroscope summarized 2738bb7.