Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Snyk] Upgrade zod from 3.22.4 to 3.23.5 #18

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Upgrade zod from 3.22.4 to 3.23.5 #18

wants to merge 1 commit into from
+5 −5

Conversation

stephan-rz
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade zod from 3.22.4 to 3.23.5.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 62 versions ahead of your current version.

  • The recommended version was released 23 days ago, on 2024-04-29.

Release notes
Package name: zod
  • 3.23.5 - 2024-04-29

    Commits:

  • 3.23.4 - 2024-04-23

    Commits:

  • 3.23.3 - 2024-04-22

    Commits:

  • 3.23.2 - 2024-04-22

    Commits:

  • 3.23.1 - 2024-04-22

    This changes the default generics back to any to prevent breakages with common packager like @ hookform/resolvers:

    - class ZodType<Output = unknown, Def extends ZodTypeDef = ZodTypeDef, Input = unknown> {}
+ class ZodType<Output = any, Def extends ZodTypeDef = ZodTypeDef, Input = any> {}

    Commits:

  • 3.23.0 - 2024-04-21

    Zod 3.23 is now available. This is the final 3.x release before Zod 4.0. To try it out:

    npm install zod

    Features

    z.string().date()

    Zod can now validate ISO 8601 date strings. Thanks @ igalklebanov! #1766

    const schema = z.string().date();
schema.parse("2022-01-01"); // OK

    z.string().time()

    Zod can now validate ISO 8601 time strings. Thanks @ igalklebanov! #1766

    const schema = z.string().time();
schema.parse("12:00:00"); // OK

    You can specify sub-second precision using the precision option:

    const schema = z.string().time({ precision: 3 });
schema.parse("12:00:00.123"); // OK
schema.parse("12:00:00.123456"); // Error
schema.parse("12:00:00"); // Error

    z.string().duration()

    Zod can now validate ISO 8601 duration strings. Thanks @ mastermatt! #3265

    const schema = z.string().duration();
schema.parse("P3Y6M4DT12H30M5S"); // OK

    Improvements to z.string().datetime()

    Thanks @ bchrobot #2522

    You can now allow unqualified (timezone-less) datetimes using the local: true flag.

    const schema = z.string().datetime({ local: true });
schema.parse("2022-01-01T12:00:00"); // OK

    Plus, Zod now validates the day-of-month correctly to ensure no invalid dates (e.g. February 30th) pass validation. Thanks @ szamanr! #3391

    z.string().base64()

    Zod can now validate base64 strings. Thanks @ StefanTerdell! #3047

    const schema = z.string().base64();
schema.parse("SGVsbG8gV29ybGQ="); // OK

    Improved discriminated unions

    The following can now be used as discriminator keys in z.discriminatedUnion():

    • ZodOptional
    • ZodNullable
    • ZodReadonly
    • ZodBranded
    • ZodCatch
    const schema = z.discriminatedUnion("type", [
  z.object({ type: z.literal("A").optional(), value: z.number() }),
  z.object({ type: z.literal("B").nullable(), value: z.string() }),
  z.object({ type: z.literal("C").readonly(), value: z.boolean() }),
  z.object({ type: z.literal("D").brand<"D">(), value: z.boolean() }),
  z.object({ type: z.literal("E").catch("E"), value: z.unknown() }),
]);

    Misc

    Breaking changes

    There are no breaking changes to the public API of Zod. However some changes can impact ecosystem tools that rely on Zod internals.

    ZodFirstPartySchemaTypes

    Three new types have been added to the ZodFirstPartySchemaTypes union. This may impact some codegen libraries. #3247

    +  | ZodPipeline<any, any>
+  | ZodReadonly<any>
+  | ZodSymbol;

    Unrecognized keys in .pick() and .omit()

    This version fixes a bug where unknown keys were accidentally accepted in .pick() and omit(). This has been fixed, which could cause compiler errors in some user code. #3255

    z.object({ 
  name: z.string() 
}).pick({
  notAKey: true // no longer allowed
})

    Bugfixes and performance

    Docs and ecosystem

    New Contributors

@snyk-bot
fix: upgrade zod from 3.22.4 to 3.23.5
e3cca26 
Snyk has created this PR to upgrade zod from 3.22.4 to 3.23.5.

See this package in npm:
zod

See this project in Snyk:
https://app.snyk.io/org/shamalchathuranga2/project/5564b192-b36b-4f09-842a-db1c9df41fea?utm_source=github&utm_medium=referral&page=upgrade-pr
@vercel Vercel
Copy link

vercel bot commented May 22, 2024 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
secure-messaging-app ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 22, 2024 2:34pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Prisma XOR with Zod > 3.21.1 not working
2 participants
@stephan-rz @snyk-bot