Conversation
cd9f644 to
6dcfe69
Compare
| "tldts": "^7.0.12", | ||
| "web-ext": "^8.9.0", | ||
| "zod": "^3.25.67" | ||
| "zod": "^4.3.6" |
There was a problem hiding this comment.
ZodError .errors property removed in Zod 4
High Severity
The upgrade from Zod 3 to Zod 4 introduces a breaking change that will cause a runtime error. The codebase at shared/js/background/classes/tracker-stats.js line 179 uses result.error.errors.length, but in Zod 4, the .errors alias on ZodError has been removed. The official Zod 4 documentation shows ZodError now only has .issues. When validation fails, accessing .errors will return undefined, causing a TypeError: Cannot read property 'length' of undefined.
Please tell me if this was useful or not with a 👍 or 👎.
Bumps [zod](https://github.com/colinhacks/zod) from 3.25.67 to 4.3.6. - [Release notes](https://github.com/colinhacks/zod/releases) - [Commits](colinhacks/zod@v3.25.67...v4.3.6) --- updated-dependencies: - dependency-name: zod dependency-version: 4.3.6 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
6dcfe69 to
365a209
Compare
| "tldts": "^7.0.12", | ||
| "web-ext": "^8.9.0", | ||
| "zod": "^3.25.67" | ||
| "zod": "^4.3.6" |
There was a problem hiding this comment.
Major zod v3→v4 bump without source code migration
High Severity
This bumps zod across a major version (v3 → v4) with no corresponding source code changes. The codebase uses z.discriminatedUnion('messageType', [...]) in shared/js/newtab/schema.js, which relies on the v3 two-argument API where the discriminator key is the first argument. In v4, z.discriminatedUnion was reworked to auto-detect the discriminator and primarily accepts a single array argument. Other v4 breaking changes — including .default() behavior within optional fields and error structure changes — could also cause subtle runtime regressions in shared/js/background/classes/tracker-stats.js where .default(0) and .default([]) are used inside z.object().
Please tell me if this was useful or not with a 👍 or 👎.


Bumps zod from 3.25.67 to 4.3.6.
Release notes
Sourced from zod's releases.
... (truncated)
Commits
ca3c862v4.3.6762e911Generalize numeric key handlingdfbbf1cAvoid re-exported star modules (#5656)cbf77bbAvoid non null assertion (#5638)85db85efix: typo in codec.test.ts file (#5628)edd4132fix: add missing User-agent to robots.txt and allow all (#5646)251d716Clean up workflow_callf4b7baeUpdate pullfrog.yml (#5634)9977fb0Add brand.dev to sponsors0cdc0b84.3.5Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Note
Medium Risk
Major-version upgrade of a runtime schema/validation library may introduce API/behavior changes that can break validation or parsing at runtime. Lockfile churn is otherwise mechanical.
Overview
Bumps the
zoddependency from3.25.xto4.3.6inpackage.json.Updates
package-lock.jsonaccordingly, including resolvingchromium-bidito use its own nestedzod@3.25.76while the root dependency moves tozod@4.3.6, and removing some now-unneeded lockfile entries underaddons-linter.Written by Cursor Bugbot for commit 365a209. This will update automatically on new commits. Configure here.