8000 chore(deps): update all non-major dependencies by renovate[bot] · Pull Request #217 · romhml/compodium · GitHub
[go: up one dir, main page]
Skip to content

chore(deps): update all non-major dependencies - #217

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/all-minor-patch
Aug 31, 2026
Merged

chore(deps): update all non-major dependencies#217
renovate[bot] merged 1 commit into
mainfrom
renovate/all-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 Type Update Pending
@nuxt/content (source) ^3.15.2 → ^3.16.0 age confidence dependencies minor
@nuxt/test-utils ^4.1.0 → ^4.2.0 age confidence devDependencies minor
@takumi-rs/core (source) 2.12.0 → 2.13.0 age confidence dependencies minor 2.13.3 (+2)
@takumi-rs/wasm 2.12.0 → 2.13.0 age confidence dependencies minor 2.13.3 (+2)
@types/node (source) ^26.2.0 → ^26.4.0 age confidence devDependencies minor
@vue/compiler-sfc (source) ^3.5.41 → ^3.5.42 age confidence dependencies patch
eslint (source) ^10.9.0 → ^10.9.1 age confidence devDependencies patch
node 24.19.0 → 24.20.0 age confidence uses-with minor
vue-router (source) ^5.2.0 → ^5.3.0 age confidence dependencies minor
wrangler (source) ^4.125.0 → ^4.127.1 age confidence devDependencies minor
zod (source) ^4.4.3 → ^4.5.2 age confidence dependencies minor 4.5.4 (+1)

Release Notes

nuxt/content (@​nuxt/content)

v3.16.0

Compare Source

Bug Fixes
  • avoid install prompt in non-interactive environments (#​3833) (2d0e84b)
  • ContentRenderer: keep async component identity stable across re-resolves (#​3835) (dcf86e6)
  • improve generated git cache key (#​3839) (d1e353e)
  • module: keep content templates when building with _prepare (#​3837) (e390c3b)
  • nuxthub: handle object form of hub.db (#​3822) (8841abc)
  • query: tolerate trailing slashes in path-based lookups (#​3838) (220d392)
  • runtime: use dynamic import for #content/adapter to prevent prerender failure (#​3830) (400390a)
  • use UTC getters in formatDate/formatDateTime to prevent timezone drift (#​3782) (9f1f89a)
nuxt/test-utils (@​nuxt/test-utils)

v4.2.0

Compare Source

v4.2.0 is the next minor release.

👉 Changelog

compare changes

🚀 Enhancements
  • browser: add render helper for vitest browser mode (#​1725)
  • runtime-utils: add spy option to mount + render helpers (#​1762)
🩹 Fixes
  • runtime-utils: mockNuxtImport sourcemap mapped position (#​1787)
  • config: tolerate non-cloneable values when cloning config (#​1771)
  • e2e: honour setupTimeout in playwright + surface server logs (#​1785)
  • e2e: add explanation if server exited before being ready (#​1761)
  • module: handle string presets in auto-imports (#​1784)
  • config: don't run includeSource in both projects in defineVitestConfig (#​1763)
  • e2e: use taskkill to kill processes on windows (#​1760)
  • config: support nuxt v5 with nitro vite environment (#​1758)
🏡 Chore
  • avoid missing file extension warning in test/examples (#​1775)
  • exempt first-party packages from pnpm minimumReleaseAge (#​1774)
  • replace latest ranges with caret ranges (#​1773)
  • move vite environment api tests to example tests (#​1755)
✅ Tests
  • re-enable bun browser e2e on windows (#​1791)
🤖 CI
  • migrate to uppt for release workflow (#​1792)
🎉 New Contributors
❤️ Contributors
kane50613/takumi (@​takumi-rs/core)

v2.13.0

Resolve tw utilities through CSS variables

Utilities now read the CSS variables Tailwind compiles them to, falling back to the built-in value. Define tokens in :root. --color-brand-500 makes bg-brand-500 work, and spacing, fonts, shadows, animations and breakpoints follow the same rule.

Gradients now match Tailwind on two counts. Stops alone no longer paint without bg-linear-*, bg-radial or bg-conic, and a missing to stop fades to transparent.

Let stylesheet rules win over tw utilities

Utilities now sit in the last cascade layer, below unlayered CSS and above rules in a named @layer. Important reverses that order. An important utility beats unlayered important CSS but loses to one in a named layer. Inline important declarations stay on top. A template that relied on tw beating a matching rule needs a fix. Move that rule into a layer, or mark the utility !.

Honor !important in inline styles

An inline !important declaration now outranks important rules and animations. Both the style object and an HTML style attribute read the marker.

Inherit text-fit from a parent

text-fit now inherits. Descendant text uses the inherited value to calculate its scale.

Parse @theme blocks as :root rules

A Tailwind v4 source stylesheet now works in css without compiling it first. @theme declarations land on :root, and @keyframes inside the block register. Modifiers like reference read the same way. The prefix() modifier is not supported.

Wrap box-sizing: content-box text inside its padding

A box with box-sizing: content-box and horizontal padding wrapped its text
against the border box, so the text took fewer lines than it needed and
overflowed the bottom of the box.

Cut allocations in style property parsing

Parsing a string-valued property copied the value before handing it to cssparser. Normalizing a kebab-case or camelCase property name allocated a second string just to trim leading underscores. String values now parse in place, and names normalize in one allocation.

Compose filters and transforms through custom properties

Filter, translate, scale and grid-line utilities now compose through --tw-* variables like Tailwind's compiled CSS. Stacked filters follow Tailwind's fixed chain order instead of class order.

Size auto table columns by their content

An all-auto table shared its free space evenly, so a one-word column took as
much room as a paragraph. Each column now grows in proportion to its
max-content width, the way Blink distributes it, and never below the widest
word it has to hold. A table narrower than its content still approximates.

Escape control characters in serialized CSS strings

A quoted string containing a newline left it unescaped. This produced invalid CSS. CSS strings now use cssparser's escaping.

Write a css entry as an object

A css entry can be a rule, { selector, style, rules }, or an animation, { keyframes, steps }. Takumi checks the selector and every value before the entry reaches the parser, so a token that comes from application data cannot escape the rule it was written for. The keyframes option is deprecated and goes away in v3.

Turn on Preflight through @import "tailwindcss"

The import line at the top of a Tailwind v4 stylesheet now works. Preflight replaces the UA preset. Margins and padding go, lists lose their markers, and h1 through h6 drop their font sizing. It also brings the universal border reset, link and table resets, block-level images, and hidden on any element. Author rules outrank Preflight, apart from hidden, which it marks important. Other @import targets stay unsupported.

Support the disclosure-open and disclosure-closed counter styles

list-style-type now accepts disclosure-open and disclosure-closed, drawing the triangles CSS Counter Styles defines. disclosure-closed points the way the text runs, so it flips under direction: rtl. Font subsetting covers all three characters.

Report text runs for a node that holds text directly

measure returned no text runs for <div>word</div>, the shape an HTML parse
produces most often, while <div><span>word</span></div> reported them. The
render was correct either way; only the measurement was missing its geometry.

Support legacy WebKit box alignment properties

Map -webkit-box-orient to flex-direction, -webkit-box-pack to justify-content, and -webkit-box-align to align-items.

Stop a box narrower than its padding from panicking

A box whose horizontal padding exceeds its own width left the text a negative
width to lay out in, which tripped an assertion inside the text layouter and
crashed the render. The width the text lays out against now stops at zero.

Write a group of css entries as an object

A css entry can be { media, rules }, { supports, rules }, or { layer, rules }. A layer without rules declares its order alone. Takumi reads each prelude with the grammar its rule takes, so it cannot close the rule and open another.

Expand @apply inside stylesheet rules

.card { @apply mt-4 bg-brand-500; } now expands through the tw parser where it is written, ! suffix included. Variants like md: are rejected. A static render has nothing for them to gate on.

Rename the stylesheets render option to css

css takes inline CSS as one string or a list. The old stylesheets name still works everywhere and warns once on takumi-js and takumi-pdf.

Support legacy WebKit display values

Map -webkit-box and -webkit-flex to flex, and -webkit-inline-box and -webkit-inline-flex to inline-flex.

Render <text> elements in SVG image sources

SVG images with <text>, <tspan> and textPath now draw their text using
the registered fonts instead of dropping it. Glyphs render from font outlines;
color emoji glyphs inside SVG text are not supported.

Accept CSS-wide keywords on shorthand properties

margin: inherit, padding: initial and border: unset were rejected. Only longhands took CSS-wide keywords. A shorthand now expands the keyword across the longhands it targets.

Reject trailing content in style values

A style object accepted width: "55px zzz", applied 55px, and ignored the rest. It now rejects the whole value, the way a stylesheet already drops such a declaration. A substituted var() value follows the same rule.

Take an inline-block's baseline from the lines it actually laid out

An inline-block with horizontal padding re-wrapped its content against the
border box to find its baseline, so text beside it aligned with the wrong line.

vuejs/core (@​vue/compiler-sfc)

v3.5.42

Compare Source

Bug Fixes
eslint/eslint (eslint)

v10.9.1

Compare Source

actions/node-versions (node)

v24.20.0: 24.20.0

Compare Source

Node.js 24.20.0

vuejs/router (vue-router)

v5.3.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub
cloudflare/workers-sdk (wrangler)

v4.127.1

Compare Source

Patch Changes

v4.127.0

Compare Source

Minor Changes

  • #​15356 fe265f8 Thanks @​rubuy-74! - Add support for configuring a per-workflow max concurrency limit via workflows[].concurrency.limit in your Wrangler config.

    The limit is the maximum number of Workflow instances that can run concurrently. It is validated as a positive integer and persisted on deploy; the ceiling is enforced server-side. Concurrency is ignored in local development.

    {
  "workflows": [
    {
      "binding": "MY_WORKFLOW",
      "name": "my-workflow",
      "class_name": "MyWorkflow",
      "concurrency": { "limit": 10 }
    }
  ]
}
Patch Changes

  • #​15367 412c79e Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260825.1 ^5.20260826.1
    workerd 1.20260825.1 1.20260826.1

  • #​15375 92874f6 Thanks @​WillTaylorDev! - Upload wrangler preview modules as multipart form data

    wrangler preview used to base64 the bundle, its modules, and any sourcemaps into a single JSON request body. Base64 inflates content by a third, so a Worker with a large sourcemap could exceed the API request size limit and fail to deploy.

    The preview deployment request is now multipart/form-data. The deployment settings travel in a metadata part and each module follows as its own part carrying raw bytes, matching how wrangler deploy already uploads a Worker.

  • Updated dependencies [412c79e]:

v4.126.0

Compare Source

Minor Changes

  • #​15332 d1cc3af Thanks @​pombosilva! - Add default_retention to Workflow bindings for configuring how long instances are retained

    Workflow instances are retained for an account-wide default period after they finish. You can now set a per-Workflow default in your Wrangler configuration, applied to instances that do not specify their own retention:

    {
  "workflows": [
    {
      "binding": "MY_WORKFLOW",
      "name": "my-workflow",
      "class_name": "MyWorkflow",
      "default_retention": {
        "success_retention": "3 days",
        "error_retention": "7 days"
      }
    }
  ]
}

    Each side is optional and accepts either a duration string such as "3 days" or a whole number of milliseconds. Durations are interpreted by the Workflows API, which also caps them at your account's retention limit.

  • #​15064 693ca29 Thanks @​tpmmorris! - Include a chronological list of handler events in email test harness results, so programmatic local email tests can assert the order in which messages are received, forwarded, replied to, or rejected.

    const result = await server.getWorker().email({
  from: "sender@example.com",
  to: "inbox@example.com",
  raw: [
    "From: Sender <sender@example.com>",
    "To: Inbox <inbox@example.com>",
    "Message-ID: <test@example.com>",
    "Subject: Test email",
    "",
    "Hello from the test harness",
  ].join("\r\n"),
});

expect(result.events).toEqual([
  { type: "received", timestamp: expect.any(String) },
  {
    type: "forward",
    timestamp: expect.any(String),
    messageId: expect.any(String),
  },
  {
    type: "reply",
    timestamp: expect.any(String),
    messageId: expect.any(String),
  },
]);

  • #​15065 ad89456 Thanks @​mtlemilio! - Add experimental wrangler hyperdrive planetscale signature for provisioning Cloudflare-billed PlanetScale databases

    wrangler hyperdrive planetscale signature prints a signed authorization as JSON, proving to PlanetScale that Cloudflare will be billed for the database you are about to create:

    npx wrangler hyperdrive planetscale signature | \
  pscale database create <name> \
    --org <org> \
    --engine postgresql \
    --cloudflare-billing @- \
    --format json

    pscale database create defaults to Vitess, so pass --engine postgresql for a Postgres database, and --format json is recommended when the output is consumed by an agent.

    This requires pscale v0.313.0 or newer. Wrangler authorizes the Cloudflare billing side only, so your PlanetScale credentials stay between you and pscale.

    The signature is a cryptographically signed token that authorizes creating a database billed to your Cloudflare account. Treat it as a credential and do not share it. Piping it, as above, is recommended over passing it as a command line argument.

    This command is experimental and its interface may change.

  • #​15134 c66d2d5 Thanks @​gpanders! - Enable FUSE-capable local container development

    Miniflare now automatically passes the Docker privileges needed for FUSE to local Durable Object containers when using local rootless Docker on Linux with /dev/fuse available, or a local Docker engine on macOS or through WSL where Linux containers run in a VM. This applies to Wrangler, the Cloudflare Vite plugin, and direct Miniflare use.

  • #​15326 9fcb1c9 Thanks @​jamesopstad! - Record the selected mode in the Build Output Specification top-level config.json

    The mode a build was produced in is now written to .cloudflare/output/v0/config.json as a mode field, alongside the account and compliance settings.

  • #​14966 a4c3458 Thanks @​yomna-shousha! - Add pull request metadata to wrangler preview deployments

    wrangler preview now detects the pull request associated with the current CI run (GitHub Actions, GitLab CI, CircleCI, and a generic PULL_REQUEST_URL/PR_URL/CHANGE_URL fallback) and attaches it, along with the repository URL, to the preview deployment as annotations (workers/pull_request_number, workers/pull_request_url, workers/repository_url).

    This is best effort: if no pull request can be detected, nothing changes. When a pull request is detected, its URL is now also shown in the wrangler preview command output.

  • #​15307 433fa98 Thanks @​for-the-kidz! - Add pull request title to wrangler preview deployment annotations

    wrangler preview now also detects the title of the pull/merge request associated with the current CI run (GitHub Actions and GitLab CI, plus a generic PULL_REQUEST_TITLE fallback) and attaches it to the preview deployment as the workers/pull_request_title annotation, alongside the existing pull request number/URL, repository URL, and commit SHA annotations.

    This is best effort: if no pull request title can be detected, nothing changes.

Patch Changes
colinhacks/zod (zod)

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

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "on Monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

@pkg-pr-new
pkg-pr-new Bot commented Aug 31, 2026
Copy link
Copy Markdown 
npm i https://pkg.pr.new/romhml/compodium/@compodium/core@217

npm i https://pkg.pr.new/romhml/compodium/@compodium/examples@217

npm i https://pkg.pr.new/romhml/compodium/@compodium/nuxt@217

npm i https://pkg.pr.new/romhml/compodium/@compodium/vue@217

971C commit: 6666edb

@renovate
renovate Bot merged commit b956b7e into main Aug 31, 2026
3 checks passed
@renovate
renovate Bot deleted the renovate/all-minor-patch branch August 31, 2026 04:32
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

0