zod-nest 1.7.0 → 1.7.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -5
- package/dist/index.js +3 -3
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +3 -3
- package/dist/index.mjs.map +1 -1
- package/package.json +16 -15
package/README.md
CHANGED
|
@@ -493,15 +493,15 @@ See [`docs/recipes/custom-openapi-overrides.md`](docs/recipes/custom-openapi-ove
|
|
|
493
493
|
|
|
494
494
|
## Compatibility matrix
|
|
495
495
|
|
|
496
|
-
`zod-nest` declares explicit min + max peer-dep ranges in `package.json`: `zod >=4.4.0 <5.0.0`, `@nestjs/common >=11.0.1 <12.0.0`, `@nestjs/core >=11.0.1 <12.0.0`, `@nestjs/swagger >=11.0.0 <12.0.0`, `rxjs >=7.
|
|
496
|
+
`zod-nest` declares explicit min + max peer-dep ranges in `package.json`: `zod >=4.4.0 <5.0.0`, `@nestjs/common >=11.0.1 <12.0.0`, `@nestjs/core >=11.0.1 <12.0.0`, `@nestjs/swagger >=11.0.0 <12.0.0`, `rxjs >=7.6.0 <8.0.0`, `reflect-metadata >=0.2.0 <0.3.0`, Node `>=22`. CI validates those claims by running the full test suite against the cells below; a red cell is a real blocker. Upper bounds are deliberate — a new peer major has to land in a real PR with a `/check-upstream-updates` audit before consumers can install it against this library.
|
|
497
497
|
|
|
498
498
|
| Cell | `zod` | `@nestjs/common` | `@nestjs/core` | `@nestjs/swagger` | `rxjs` | `reflect-metadata` |
|
|
499
499
|
|---|---|---|---|---|---|---|
|
|
500
|
-
| `floor` | 4.4.0 | 11.0.1 | 11.0.1 | 11.0.0 | 7.
|
|
501
|
-
| `zod-latest` | latest | 11.0.1 | 11.0.1 | 11.0.0 | 7.
|
|
502
|
-
| `nest-latest` | 4.4.0 | latest | latest | latest | 7.
|
|
500
|
+
| `floor` | 4.4.0 | 11.0.1 | 11.0.1 | 11.0.0 | 7.6.0 | 0.2.0 |
|
|
501
|
+
| `zod-latest` | latest | 11.0.1 | 11.0.1 | 11.0.0 | 7.6.0 | 0.2.0 |
|
|
502
|
+
| `nest-latest` | 4.4.0 | latest | latest | latest | 7.6.0 | 0.2.0 |
|
|
503
503
|
| `rxjs-latest` | 4.4.0 | 11.0.1 | 11.0.1 | 11.0.0 | latest | 0.2.0 |
|
|
504
|
-
| `reflect-metadata-latest` | 4.4.0 | 11.0.1 | 11.0.1 | 11.0.0 | 7.
|
|
504
|
+
| `reflect-metadata-latest` | 4.4.0 | 11.0.1 | 11.0.1 | 11.0.0 | 7.6.0 | latest |
|
|
505
505
|
| `all-latest` | latest | latest | latest | latest | latest | latest |
|
|
506
506
|
|
|
507
507
|
Cell definitions live in [`.github/compat-matrix.json`](.github/compat-matrix.json). The CI workflow ([`.github/workflows/compat-matrix.yml`](.github/workflows/compat-matrix.yml)) runs on every push to `main` and weekly on Monday — when a cell fails, the workflow opens (or comments on) a GitHub issue labelled `compat-matrix-failure` so the regression is tracked outside the Actions UI. Editing the JSON is the formal way to extend or shrink supported ranges. Node is not matrixed — the `>=22` floor is enforced by `engines`.
|
package/dist/index.js
CHANGED
|
@@ -1419,9 +1419,9 @@ var runPass = /* @__PURE__ */ __name((opts, io, knownIds) => {
|
|
|
1419
1419
|
const raw = zod.z.toJSONSchema(opts.registry.zodRegistry, built.options);
|
|
1420
1420
|
built.consumeUnrepresentable();
|
|
1421
1421
|
const filtered = /* @__PURE__ */ new Map();
|
|
1422
|
-
for (const id of
|
|
1423
|
-
if (
|
|
1424
|
-
filtered.set(id,
|
|
1422
|
+
for (const [id, schema] of Object.entries(raw.schemas)) {
|
|
1423
|
+
if (knownIds.has(id)) {
|
|
1424
|
+
filtered.set(id, schema);
|
|
1425
1425
|
}
|
|
1426
1426
|
}
|
|
1427
1427
|
return filtered;
|