Bump zod-openapi from 2.12.0 to 2.13.0

[dependabot]

Bumps zod-openapi from 2.12.0 to 2.13.0.

Release notes

Sourced from zod-openapi's releases.

v2.13.0

What's Changed

New Features 🎉

• Introduce same effectType by @​samchungy in samchungy/zod-openapi#217

  This library now has a new effectType when dealing with Zod Effects. In most scenarios, our users were using transform to sanitise or transform while ensuring the type did not change, however, this library could not handle this.

  The new same option allows this library to pick the input schema to produce a schema while ensuring that the input and output remain the same type.

  For example: when creating a response (output) schema for the following type this library cannot hook into the TypeScript compiler at runtime to understand that you wanted a string schema generated:

  z.string().transform((string) => string.toUpperCase());

  which meant that you had to declare the following in order to get it to work:

  z.string().transform((string) => string.toUpperCase()).openapi({ effectType: 'input' });
  // or
  z.string().transform((string) => string.toUpperCase()).pipe(z.string());

  However, in the first example this could be dangerous if a user was to change the transform to no longer be the same type:

  z.string().transform((string) => string.length).openapi({ effectType: 'input' });

  The new same type allows us to avoid this mistake:

  ✅ z.string().transform((string) => string.toUpperCase()).openapi({ effectType: 'same' });
  // Type '"same"' is not assignable to type 'CreationType | undefined'. ts(2322)
  ❌ z.string().transform((string) => string.length).openapi({ effectType: 'same' });

• Refactor Effect Handling by @​samchungy in samchungy/zod-openapi#211, samchungy/zod-openapi#214

  This library now validates that effects used within registered Lazy schemas are not included in both input and output schemas. This could possibly be a breaking change if you were accidentally doing this.

  This library should also provide clearer errors when using Zod Effects with registered components which should make it easier to make dealing with effects more pleasant.

... (truncated)

Commits

• 7510dab Release v2.13.0
• d2c20ad Introduce same effectType (#217)
• 4817955 Add default effect type handling (#216)
• a44d28e Bump @​redocly/cli from 1.8.0 to 1.8.2 (#213)
• da50e6c Default Effect Values (#215)
• e7b2de3 Handle Lazy Effects (#214)
• ea834f9 Remove duplicate descriptions on referenced schemas (#212)
• fb1fd2d Refactor Effect Handling (#211)
• bc75221 Bump @​redocly/cli from 1.6.0 to 1.8.0 (#205)
• 9cbc19d Fix duplicate parameter component check (#207)
• Additional commits viewable in compare view

Dependabot 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)