Skip to content

fix(deps): update prod minor+patch - #103

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/prod-minor+patch
Open

fix(deps): update prod minor+patch#103
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/prod-minor+patch

Conversation

@renovate

@renovate renovate Bot commented Aug 31, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@libsql/client (source) 0.17.4 → 0.18.0 age confidence
@noble/curves (source) ^2.3.0 → ^2.4.0 age confidence
@noble/hashes (source) ^2.3.0 → ^2.4.0 age confidence
@simplewebauthn/server (source) ^13.3.2 → ^13.3.3 age confidence
@tanstack/react-query (source) ^5.102.4 → ^5.102.8 age confidence
@tiptap/core (source) ^3.30.3 → ^3.31.3 age confidence
@tiptap/extension-emoji (source) ^3.30.3 → ^3.31.3 age confidence
@tiptap/pm (source) ^3.30.3 → ^3.31.3 age confidence
@tiptap/react (source) ^3.30.3 → ^3.31.3 age confidence
@tiptap/starter-kit (source) ^3.30.3 → ^3.31.3 age confidence
@tiptap/suggestion (source) ^3.30.3 → ^3.31.3 age confidence
filesize (source) ^11.0.22 → ^11.0.23 age confidence
lucide-react (source) ^1.34.0 → ^1.41.0 age confidence
mediasoup-client (source) ^3.22.0 → ^3.23.1 age confidence
react-colorful (source) ^5.8.0 → ^5.8.1 age confidence
zod (source) ^4.4.3 → ^4.5.4 age confidence

Release Notes

tursodatabase/libsql-client-ts (@​libsql/client)

v0.18.0

Compare Source

MasterKale/SimpleWebAuthn (@​simplewebauthn/server)

v13.3.3

Compare Source

Changes:

  • [server] Updated MDS blob signature verification to support more algorithms
    (#​788)
  • [server] Updated MetadataService to know about the new FIDO MDS blob trust anchor
    certificate (#​789)
ueberdosis/tiptap (@​tiptap/core)

v3.31.3

Compare Source

@​tiptap/extension-collaboration-caret
Patch Changes
  • Fixed a bug which allowed potentially unsafe color values being sent by other clients. Those unsafe colors received from collaboration users are now ignored.
@​tiptap/react
Patch Changes
  • Fix a TypeScript error (TS2694) in the shipped type declarations when skipLibCheck is turned off.

v3.31.2

Compare Source

@​tiptap/pm
Patch Changes
  • Bump prosemirror-view to ^1.42.3, which fixes an XSS vulnerability where pasting crafted HTML could run arbitrary JavaScript (GHSA-c8x8-7fp4-3x9w).

v3.31.1

Compare Source

@​tiptap/core
Patch Changes
  • Fix freezes in framework-based node views on iOS and Android

v3.31.0

Compare Source

@​tiptap/react
Minor Changes
  • e7bf804: Align selected with ProseMirror node selections by default, expose text selections through selectionInside, and keep selectedOnTextSelection compatible.

v3.30.6

Compare Source

@​tiptap/core
Patch Changes
  • Nested lists exported to Markdown now keep their hierarchy when the file is read back by other Markdown tools.
@​tiptap/extension-list
Patch Changes
  • Nested lists exported to Markdown now keep their hierarchy when the file is read back by other Markdown tools.
@​tiptap/extension-youtube
Patch Changes
  • Pasting a YouTube iframe without a src attribute no longer crashes the editor. The embed is kept without a source.
@​tiptap/markdown
Patch Changes
  • Fix Markdown serialization of whitespace-only marked text.
@​tiptap/react
Patch Changes
  • Reduce overhead in React node views on documents with many nodes.
avoidwork/filesize.js (filesize)

v11.0.23

Compare Source

  • fix: keep precision trailing zeros for negative values #331
  • chore(deps-dev): bump rollup from 4.63.0 to 4.63.1 #335
  • chore(deps-dev): bump rollup from 4.62.5 to 4.63.0 #334
  • chore(deps-dev): bump oxlint from 1.79.0 to 1.80.0 #333
  • chore(deps-dev): bump oxfmt from 0.64.0 to 0.65.0 #332
  • chore(deps-dev): bump oxlint from 1.78.0 to 1.79.0 #330
  • chore(deps-dev): bump oxfmt from 0.62.0 to 0.64.0 #329
  • chore(deps-dev): bump rollup from 4.62.4 to 4.62.5 #328
  • chore(deps-dev): bump oxlint from 1.77.0 to 1.78.0 #326
  • chore(deps-dev): bump oxfmt from 0.61.0 to 0.62.0 #325
  • chore(deps-dev): bump oxlint from 1.76.0 to 1.77.0 #324
  • chore(deps-dev): bump rollup from 4.62.3 to 4.62.4 #323
  • chore(deps-dev): bump oxlint from 1.75.0 to 1.76.0 #322
  • chore(deps-dev): bump oxfmt from 0.60.0 to 0.61.0 #321
  • chore(deps-dev): bump rollup from 4.62.2 to 4.62.3 #320
  • chore(deps-dev): bump oxfmt from 0.59.0 to 0.60.0 #319
  • chore(deps-dev): bump oxlint from 1.74.0 to 1.75.0 #318
  • chore(deps): bump actions/setup-node from 6 to 7 #317
  • chore(deps-dev): bump oxfmt from 0.58.0 to 0.59.0 #316
  • chore(deps-dev): bump oxlint from 1.73.0 to 1.74.0 #315
lucide-icons/lucide (lucide-react)

v1.41.0: Version 1.41.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.40.0...1.41.0

v1.40.0: Version 1.40.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.39.0...1.40.0

v1.39.0: Version 1.39.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@1.38.0...1.39.0

v1.38.0: Version 1.38.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@1.36.0...1.38.0

v1.37.0: Version 1.37.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.35.0...1.37.0

v1.36.0: Version 1.36.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.35.0...1.36.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.35.0...1.36.0

v1.35.0: Version 1.35.0

Compare Source

What's Changed
New Contributors

Full Changelog: lucide-icons/lucide@1.34.0...1.35.0

omgovich/react-colorful (react-colorful)

v5.8.1

Compare Source

  • Fix RGB channels drifting when only the alpha channel is changed: { r: 200, g: 120, b: 35 } no longer becomes { r: 199, g: 119, b: 34 } after moving the alpha slider. Thanks to @​t-hamano for the investigation (via #​234, fixes #​163)
colinhacks/zod (zod)

v4.5.4

Compare Source

Commits:

v4.5.3

Compare Source

v4.5.2

Compare Source

Commits:

  • a354314 fix(docs): keep blog posts out of the docs collection (#​6484)
  • d378c42 ci: drop canary publishing from the release workflow (#​6487)
  • 212b941 fix(v4): let a prototype method getter answer a bare call so vi.spyOn works (#​6488)
  • e7576f5 docs(blog): let the page show through the navbar in dark mode (#​6489)
  • fedb06f fix(docs): match the blog TOC hover bar to the 2px active indicator
  • 6c932fc chore: bump devcontainer image to Node 24 (#​6470)
  • 6635d9d docs(blog): soften the "method memoization" attribution
  • 019ae29 fix(docs): drop ISR on the docs route so the home page hydrates
  • 652bb43 chore(docs): drop the scroll log from the route-change scroller
  • 571c8e8 fix(docs): render blog tabs with the stock fumadocs tab card
  • 9a193aa 4.5.2

v4.5.1

Compare Source

Commits:

  • 2e862db ci: gate the GitHub release and JSR publish on the version being live on npm
  • 8e03380 4.5.1

v4.5.0

Compare Source

Zod 4.5 is now available.

npm install zod@latest

At a glance:

z.compile()

You can now pre-compile any Zod schema using z.compile(schema). This dramatically speeds up parsing performance.

import * as z from "zod";

const Player = z.object({
  username: z.string(),
  bio: z.string(),
  xp: z.number()
});

const CompiledPlayer = z.compile(Player);

A compiled schema can be used exactly like an uncompiled one. There are no special rules around compiled schemas. They're just faster.

Player.parse({ ... });
CompiledPlayer.parse({ ... }); // ~2x faster

On objects, arrays, and unions, this speeds up parsing by a factor of ~3–7. More complex schemas stand to benefit more than simpler ones.

Time per parse on a shared nanosecond axis, standard parser as a gray bar with the compiled time as a blue bar inside it: an array of 10 objects 377 ns to 68 ns (5.5x), a 20-key object 301 ns to 38 ns (7.8x), an array of 10 strings 241 ns to 33 ns (7.3x), a union of 3 objects 190 ns to 36 ns (5.3x), a 3-element tuple 119 ns to 33 ns (3.6x), a 5-key strict object 117 ns to 32 ns (3.7x), a discriminated union 92 ns to 27 ns (3.4x), a 5-key object 76 ns to 28 ns (2.8x); up to 7.8x faster when compiled

Time per parse by schema type, standard parser vs compiled — lower is better (benchmark)

Below are the Moltar benchmark results comparing Zod (compiled and uncompiled) against the Moltar ParseSafe bench.

Bar chart of operations per second on the moltar benchmark fixture, parseSafe category: Zod 4 compiled 47.5M, typia 45.3M, Zod 4 11.6M, valibot 1.8M, effect 1.7M, Zod 3 1.2M, arktype 152k, yup 121k

Throughput on the moltar benchmark fixture (parseSafe: returns a new object with unknown keys stripped) — higher is better (benchmark)

And the equivalent results for the Moltar AssertLoose bench. Tested against the new z.validate(schema, input) function (detailed later in the post).

Bar chart of operations per second on the moltar benchmark fixture, assertLoose category: typia 74.9M, arktype 66.2M, Zod 4 compiled 60.6M, Zod 4 6.5M, valibot 1.9M, effect 1.7M, Zod 3 1.2M, yup 124k

Throughput on the moltar benchmark fixture (assertLoose: returns a boolean, unknown keys allowed) — higher is better (benchmark)

Zod's entire test suite runs twice—once normally and again with auto-compilation enabled globally—to ensure perfect fidelity.

How it works

Under the hood, z.compile() walks the entire schema once and produces a hyperoptimized snippet of flat, loop-free JavaScript that can validate inputs far faster than a standard runtime validator. This snippet can be executed via new Function() (effectively a more powerful eval) to serve as a fast-path validator. Schemas use this to "fast check" validity, falling back to the regular runtime logic on validation failure to provide granular error information.

Take this simple Point schema:

const Point = z.object({
  x: z.number(),
  y: z.number()
});

Here is the generated snippet for it:

const isPoint = new Function("input", `
  if (typeof input !== "object" || input === null) return false;
  if (typeof input.x !== "number") return false;
  if (typeof input.y !== "number") return false;
  return true;
`);

isPoint({ x: 1, y: 2 }); // true
isPoint({ x: "1" });     // false

For the large majority of inputs, the generated function validates the data with the fastest logic JavaScript can express: straight-line typeof checks and property reads, with no interpreter in between. When it can't handle an input, Zod falls back to the standard parser.

This is the function Zod generates for the Player schema above:

if (typeof input !== "object" || input === null || Array.isArray(input)) return INVALID;
const v0 = input["username"];
if (typeof v0 !== "string") return INVALID;
const v1 = input["bio"];
if (typeof v1 !== "string") return INVALID;
const v2 = input["xp"];
if (typeof v2 !== "number" || !Number.isFinite(v2)) return INVALID;
const v3 = { "username": v0, "bio": v1, "xp": v2 };
return v3;

Armed with the power of new Function(), this happens in-process at runtime. There is no need to integrate with your build system.

The compiled schema is purely additive on top of the existing schema. It tacks on the pre-compiled fast path for checking valid inputs. When invalid data is detected, it returns the INVALID symbol to signal that parsing should fall back to the uncompiled parser. This structurally prevents subtle deviations in error reporting between compiled and uncompiled variants.

import "zod/compile"

To compile every schema in an application, import zod/compile once at the top of your entry point. Every schema constructed after that import is automatically compiled the first time it's used to parse data.

import "zod/compile"; // must come before modules that define schemas
import * as z from "zod";

const schema = z.object({ name: z.string() });
schema.parse({ name: "ok" }); // compiled on first parse

It also works as a Node.js CLI flag, which guarantees it runs before any module defines a schema:

node --import zod/compile app.js

Or set preload in bunfig.toml or nub.jsonc.

{
  "preload": ["zod/compile"]
}

All schemas benefit to varying degrees, though complex object/tuple/array schemas benefit more than simple scalar validators.

Read the docs, or the full technical writeup: Introducing z.compile()

z.creditCard()

A new string format: 12–19 digits, optionally separated by single spaces or hyphens, with a valid Luhn checksum. (#​5931)

z.creditCard().parse("4111 1111 1111 1111"); // ✅
z.creditCard().parse("4111 1111 1111 1112"); // ❌ bad checksum

z.properties()

The multi-property counterpart to z.property(). (#​5912)

const httpsUrl = z.instanceof(URL).check(
  ...z.properties({
    protocol: z.literal("https:" as string),
    hostname: z.string().regex(z.regexes.domain),
  })
);

httpsUrl.parse(new URL("https://example.com")); // ✅
httpsUrl.parse(new URL("http://localhost")); // ❌ protocol

z.deepPartial()

Back in functional form after being removed as a method in Zod 4. (#​5928)

const Post = z.object({
  title: z.string(),
  author: z.object({ name: z.string(), email: z.string() }),
});

const PartialPost = z.deepPartial(Post);
type PartialPost = z.output<typeof PartialPost>;
// => { title?: string; author?: { name?: string; email?: string } }

PartialPost.parse({ author: {} }); // ✅

The result is still a ZodObject, so .shape and .extend() keep working.

.exactPartial()

Like .partial(), but wraps each field in z.exactOptional() instead of z.optional(): keys may be omitted, but an explicit undefined is rejected. This matches TypeScript's Partial<> under exactOptionalPropertyTypes. (#​6065)

const Recipe = z.object({ title: z.string(), servings: z.number() });

const PartialRecipe = Recipe.exactPartial();
PartialRecipe.parse({});                    // ✅
PartialRecipe.parse({ title: undefined });  // ❌

In Zod Mini it's a top-level function: z.exactPartial(Recipe).

z.validate()

Standalone boolean validation, in Zod, Zod Mini, and Zod Core. It answers "is this input valid?" without constructing a ZodError, which makes rejection cheap: on invalid input it is up to 16x faster than .safeParse().success. The return type is a guard on the schema's input type, and z.validateAsync() covers schemas with async refinements. (#​6471)

z.validate(z.string(), "hi"); // true
z.validate(z.string(), 42);   // false

z.input() / z.output()

Project a schema onto its input or output side. Useful for validating the two halves of a codec independently. (#​5928)

const isoDate = z.codec(z.iso.datetime(), z.date(), {
  decode: (s) => new Date(s),
  encode: (d) => d.toISOString(),
});

const Event = z.object({ name: z.string(), at: isoDate });

z.input(Event).parse({ name: "launch", at: "2024-01-01T00:00:00Z" }); // ✅
z.output(Event).parse({ name: "launch", at: new Date() });            // ✅

This is a no-op on schemas not containing codecs/pipes.

z.toZod<T>()

A utility to define a Zod schema that agrees exactly with a static type, often one that is handwritten or externally defined. (#​5913)

type Player = { username: string; xp: number };

const Player = z.toZod<Player>()(
  z.object({
    username: z.string(),
    xp: z.number(),
  })
);

Player.shape.username; // ZodString — the schema is returned unchanged

z.getDiscriminatedOption()

Extract a discriminated union member by discriminator value. (#​5947)

const Fruit = z.object({ type: z.literal("fruit"), seeds: z.boolean() });
const Veg = z.object({ type: z.literal("vegetable"), leafy: z.boolean() });
const Produce = z.discriminatedUnion("type", [Fruit, Veg]);

z.getDiscriminatedOption(Produce, "fruit"); // typeof Fruit
z.getDiscriminatedOption(Produce, "meat");  // ❌ TypeScript error

Cyclical inputs

Zod recursive schemas now support cyclical data. For bundle size reasons, Zod Mini requires you to register a memoizer explicitly. (#​6387, #​6482)

Zod

const Category = z.object({
  name: z.string(),
  get subcategories() {
    return z.array(Category);
  },
});

const input: any = { name: "root", subcategories: [] };
input.subcategories.push(input);

const result = Category.parse(input);
result.subcategories[0] === result; // true

Zod Mini

// register a memoizer before defining any schemas
z.config({ memoizer: z.memoizer() });

const result = Category.parse(input);
result.subcategories[0] === result; // true

9x reduction in schema memory footprint

In Zod 4.4 a bare z.string() retained 7.5kb of heap. In Zod 4.5 it retains 784 bytes.

Bar chart of heap retained by one schema instance, zod 4.4.3 versus 4.5: a 10-key object 82.0kb to 11.0kb, a union 17.5kb to 2.13kb, z.string().min(1) 16.7kb to 3.37kb, a record 16.4kb to 2.64kb, z.string().optional() 12.6kb to 1.50kb, an array of strings 11.2kb to 1.93kb, z.string() 7.53kb to 784b, z.number() 4.44kb to 706b. Up to 9.8x smaller than 4.4.3.

Retained heap per schema instance, Zod 4.4.3 vs 4.5 (benchmark)

In Zod 4.4 and earlier, all schema methods were automatically bound to the instance itself. This allowed users to pluck methods from schemas without causing issues due to this-binding.

const { parse } = z.string();

parse("some data");

A consequence of this is that each bound method allocates space on the heap; method implementations are not shared across all instances via prototype, as you'd expect. Zod 4.5 implements a method memoization pattern that avoids allocating bound methods until they are actually accessed.

Read the deep dive: Reducing Zod's memory footprint by an order of magnitude

Faster failures

Zod .parse()/.safeParse() instantiates a JavaScript Error, which captures a stack trace. In the case of validation failures, this is often much slower than the parsing logic itself. When using .safeParse(), Zod no longer captures this stack trace, speeding up failure-path parses by a factor of ~7.5x. (#​6316, #​6450)

const result = Player.safeParse({ username: 42, bio: "hello", xp: 12 });
result.success; // false — ~7.5x faster than Zod 4.4
Bar chart of time per failing safeParse: zod 4.4 at 6.3 microseconds, zod 4.5 at 840 nanoseconds — 7.6x faster

Player schema (benchmark)

Symbol keys in z.object()

A shape can now declare a symbol key. TypeScript tracks it: a const symbol infers as unique symbol, so z.infer makes the key required and checks its value type. Undeclared symbol keys are still ignored. (#​6448)

const TAG = Symbol("tag");
const schema = z.object({ name: z.string(), [TAG]: z.number() });

schema.parse({ name: "alice", [TAG]: 42 }); // ✅ { name: "alice", [TAG]: 42 }
schema.safeParse({ name: "alice" });        // ❌ the symbol key is required

Bug fixes

All of these fix soundness issues, so a schema that relied on the old behavior may now reject input it used to accept.

⚠️ z.iso.datetime() requires seconds

RFC 3339 mandates seconds. z.iso.datetime() and z.iso.datetime({ offset: true }) no longer accept minute-precision input like 2020-01-01T06:15Z. local: true still admits 2020-01-01T06:15, since an unqualified datetime is outside RFC 3339 either way. ([

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Europe/Lisbon)

  • Branch creation
    • "before 5am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/prod-minor+patch branch 15 times, most recently from a00b8a4 to 58153ad Compare September 6, 2026 14:05
@renovate
renovate Bot force-pushed the renovate/prod-minor+patch branch from 58153ad to db046cf Compare September 7, 2026 14:28
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.

0 participants