fix(deps): upgrade npm packages #19

renovate · 2025-10-22T04:57:39Z

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@cloudflare/workers-types	`4.20251014.0` -> `4.20251223.0`
jose	`6.1.0` -> `6.1.3`
wrangler (source)	`4.44.0` -> `4.56.0`

Release Notes

cloudflare/workerd (@cloudflare/workers-types)

panva/jose (jose)

`v6.1.3`

Compare Source

Refactor

avoid export * as for google closure's compiler sake (6303d98), closes #832

`v6.1.2`

Compare Source

Refactor

fallback to checking instanceof for CryptoKey (901cd90), closes #765 #803 #821 #827 #828

`v6.1.1`

Compare Source

Documentation

add link to RFC9864 (767edde)
link to ML-DSA for JOSE (ed4252c)
remove mention of Edge Runtime from the readme (94fdde7)
update README.md (25098ef)

Refactor

eliminate named exports in the source code (f6ae30d)
expose setKeyManagementParameters also on a GeneralEncrypt Recipient (16e6b23)
faster path for symmetric key checks (a44c2ec)
improve en/decoding overheads (daee426)

cloudflare/workers-sdk (wrangler)

`v4.56.0`

Compare Source

Minor Changes

#11196 171cfd9 Thanks @emily-shen! - For containers being created in a FedRAMP high environment, registry credentials are encrypted by the container platform.
Update wrangler to correctly send a request to configure a registry for FedRAMP containers.
#11646 472cf72 Thanks @vovacf201! - feat: add R2 Data Catalog snapshot expiration commands

Adds new commands to manage automatic snapshot expiration for R2 Data Catalog tables:
- wrangler r2 bucket catalog snapshot-expiration enable - Enable automatic snapshot expiration
- wrangler r2 bucket catalog snapshot-expiration disable - Disable automatic snapshot expiration
Snapshot expiration helps manage storage costs by automatically removing old table snapshots while keeping a minimum number of recent snapshots for recovery purposes.

Example usage:
```
# Enable snapshot expiration for entire catalog (keep 10 snapshots, expire after 5 days)
wrangler r2 bucket catalog snapshot-expiration enable my-bucket --token $R2_CATALOG_TOKEN --max-age 7200 --min-count 10

# Enable for specific table
wrangler r2 bucket catalog snapshot-expiration enable my-bucket my-namespace my-table --token $R2_CATALOG_TOKEN --max-age 2880 --min-count 5

# Disable snapshot expiration
wrangler r2 bucket catalog snapshot-expiration disable my-bucket
```

Patch Changes

#11649 428ae9e Thanks @ascorbic! - fix: respect TypeScript path aliases when resolving non-JS modules with module rules

When importing non-JavaScript files (like .graphql, .txt, etc.) using TypeScript path aliases defined in tsconfig.json, Wrangler's module-collection plugin now correctly resolves these imports. Previously, path aliases were only respected for JavaScript/TypeScript files, causing imports like import schema from '~lib/schema.graphql' to fail when using module rules.
#11647 c0e249e Thanks @dario-piotrowicz! - The auto-configuration logic present in wrangler setup and wrangler deploy --x-autoconfig cannot reliably handle Hono projects, so in these cases make sure to properly error saying that automatically configuring such projects is not supported.
#11694 3853200 Thanks @dario-piotrowicz! - fix: improve the open-next detection that wrangler deploy performs to eliminate false positives for non open-next projects
Updated dependencies [ae1ad22, 737c0f4]:
- miniflare@4.20251217.0

`v4.55.0`

Compare Source

Minor Changes

#11301 6c590a0 Thanks @dario-piotrowicz! - Make wrangler deploy run opennextjs-cloudflare deploy when executed in an open-next project
#11045 12a63ef Thanks @edmundhung! - Add an internal unstable_printBindings API for vite plugin integration
#11590 7d8d4a6 Thanks @pombosilva! - Add Workflows send-event to wrangler commands.
#11301 6c590a0 Thanks @dario-piotrowicz! - Support Next.js (via OpenNext) projects in autoconfig

Patch Changes

#11615 ed42010 Thanks @elithrar! - Add helpful warning when SSL certificate errors occur due to corporate proxies or VPNs intercepting HTTPS traffic. When errors like "self-signed certificate in certificate chain" are detected, wrangler now displays guidance about installing missing system roots from your corporate proxy vendor.
#11641 6b28de1 Thanks @petebacondarwin! - update command status text and formatting
#11578 4201472 Thanks @gpanders! - Fixup UX papercuts in containers SSH
#11550 95d81e1 Thanks @hiendv! - Fix "TypeError: Body is unusable: Body has already been read" when failing to exchange oauth code because of double response.text().
Updated dependencies [5d085fb, b75b710, 1e9be12]:
- miniflare@4.20251213.0

`v4.54.0`

Compare Source

Minor Changes

#11512 c15e99e Thanks @emily-shen! - Enable using ctx.exports with containers

You can now use containers with Durable Objects that are accessed via ctx.exports.

Now your config file can look something like this:

{
	"name": "container-app",
	"main": "src/index.ts",
	"compatibility_date": "2025-12-01",
	"compatibility_flags": ["enable_ctx_exports"], // compat flag needed for now.
	"containers": [
		{
			"image": "./Dockerfile",
			"class_name": "MyDOClassname",
			"name": "my-container"
		},
	],
	"migrations": [
		{
			"tag": "v1",
			"new_sqlite_classes": ["MyDOClassname"],
		},
	],
	// no need to declare your durable object binding here
}

Note that when using ctx.exports, where you previously accessed a Durable Object via something like env.DO, you should now access with ctx.exports.MyDOClassname.

Refer to the docs for more information on using ctx.exports.

#11508 b17797c Thanks @dario-piotrowicz! - Wrangler will no longer try to add additional configuration to projects using @cloudflare/vite-plugin when deploying or running wrangler setup
#11508 b17797c Thanks @dario-piotrowicz! - When a Vite project is detected, install @cloudflare/vite-plugin
#11576 bb47e20 Thanks @dario-piotrowicz! - Support Analog projects in autoconfig
#10582 991760d Thanks @flakey5! - Add containers ssh command

Patch Changes

#11467 235d325 Thanks @edmundhung! - fix: prevent reporting SQLite error from wrangler d1 execute to Sentry
#11414 41103f5 Thanks @petebacondarwin! - add extra logging to user log-in flow for diagnosing failed login requests
#11559 ea6fbec Thanks @nikitassharma! - Remove image validation for containers on wrangler deploy.

Internal customers are able to use additional image registries and will run into failures with this validation. Image registry validation will now be handled by the API.
Updated dependencies [31c162a, bd5f087, c6dd86f]:
- miniflare@4.20251210.0

`v4.53.0`

Compare Source

Minor Changes

#11500 af54c63 Thanks @dario-piotrowicz! - Add new autoconfig_summary field to the deploy output entry

This change augments wrangler deploy output being printed to WRANGLER_OUTPUT_FILE_DIRECTORY or WRANGLER_OUTPUT_FILE_PATH to also include a new autoconfig_summary field containing the possible summary details for the autoconfig process (the field is undefined if autoconfig didn't run).

Note: the field is experimental and could change while autoconfig is not GA
#11477 9988cc9 Thanks @ascorbic! - Support Nuxt in autoconfig
#11472 ce295bf Thanks @dario-piotrowicz! - Support Qwik projects in autoconfig
#10937 9514c9a Thanks @ReppCodes! - Add support for "targeted" placement mode with region, host, and hostname fields

This change adds a new mode to placement configuration. You can specify one of the following fields to target specific external resources for Worker placement:
- region: Specify a region identifier (e.g., "aws:us-east-1") to target a region from another cloud service provider
- host: Specify a host with (required) port (e.g., "example.com:8123") to target a TCP service
- hostname: Specify a hostname (e.g., "example.com") to target an HTTP resource
These fields are mutually exclusive - only one can be specified at a time.

Example configuration:
```
[placement]
host = "example.com:8123"
```
#11498 ac861f8 Thanks @penalosa! - Add React Router support in autoconfig
#11506 79d30d4 Thanks @vicb! - Set the target JS version to ES2024

Patch Changes

#11393 45480b1 Thanks @alsuren! - improved --help text for wrangler d1 subcommands
#11523 94c67e8 Thanks @jamesopstad! - fix: types from @cloudflare/workers-utils not being exported correctly from Wrangler
#11483 f550b62 Thanks @edmundhung! - stop running npm install with --legacy-peer-deps flag when setting up a project
Updated dependencies [819e287, 56e78c8, 0aa959a]:
- @cloudflare/unenv-preset@2.7.13
- miniflare@4.20251202.1

`v4.52.1`

Compare Source

Patch Changes

#11504 7e80340 Thanks @dario-piotrowicz! - Fix wrangler deploy failing for new workers containing environment variables or bindings
Updated dependencies [59534ba]:
- miniflare@4.20251202.0

`v4.52.0`

Compare Source

Minor Changes

#11416 abe49d8 Thanks @dario-piotrowicz! - Remove the wrangler deploy's --x-remote-diff-check experimental flag

The remote diffing feature has been enabled by default for a while and its functionality is stable, as a result the experimental flag (only available for option-out of the feature right now) has been removed.
#11408 f29e699 Thanks @ascorbic! - Export unstable helpers useful for generating wrangler config
#11389 2342d2f Thanks @dario-piotrowicz! - Improve the wrangler deploy flow to also check for potential overrides of secrets.

Now when you run wrangler deploy Wrangler will check the remote secrets for your workers for conflicts with the names of the bindings you're about to deploy. If there are conflicts, Wrangler will warn you and ask you for your permission before proceeding.
#11375 9a1de61 Thanks @penalosa! - Support TanStack Start in autoconfig
#11360 6b38532 Thanks @emily-shen! - Containers: Allow users to directly authenticate external image registries in local dev

Previously, we always queried the API for stored registry credentials and used those to pull images. This means that if you are using an external registry (ECR, dockerhub) then you have to configure registry credentials remotely before running local dev.

Now you can directly authenticate with your external registry provider (using docker login etc.), and Wrangler or Vite will be able to pull the image specified in the containers.image field in your config file.

The Cloudflare-managed registry (registry.cloudflare.com) currently still does not work with the Vite plugin.
#11009 e4ddbc2 Thanks @dario-piotrowicz! - Allow users to provide an account_id as part of the WorkerConfigObject they pass to maybeStartOrUpdateRemoteProxySession
#11478 2aec2b4 Thanks @dario-piotrowicz! - Support SolidStart in autoconfig
#11330 5a873bb Thanks @dario-piotrowicz! - Support Angular projects in autoconfig
#11449 e7b690b Thanks @penalosa! - Delegate generation of HTTPS certificates to Miniflare
#11448 2b4813b Thanks @edmundhung! - Bumps esbuild version to 0.27.0
#11335 c47ad11 Thanks @dario-piotrowicz! - Support internal-only undocumented cross_account_grant service binding property
#11346 a977701 Thanks @penalosa! - We're soon going to make backend changes that mean that wrangler dev --remote sessions will no longer have an associated inspector connection. In advance of these backend changes, we've enabled a new wrangler tail-based logging strategy for wrangler dev --remote. For now, you can revert to the previous logging strategy with wrangler dev --remote --no-x-tail-logs, but in future it will not be possible to revert.

The impact of this will be that logs that were previously available via devtools will now be provided directly to the Wrangler console and it will no longer be possible to interact with the remote Worker via the devtools console.

Patch Changes

#11397 b154de2 Thanks @vicb! - Use more workerd native modules

Node modules punycode, trace_events, cluster, wasi, and domains will be used when enabled
via a compatibility flag or by default when the compatibility date is greater or equal to 2025-12-04.
#11452 76f0540 Thanks @penalosa! - Remove uses of eval() from the Wrangler bundle
#11284 695fa25 Thanks @dom96! - Removes duplicate module warnings when vendoring Python packages
#11249 504e258 Thanks @dario-piotrowicz! - fix: Generalize autoconfig wording

Generalize the autoconfig wording so that when it doesn't specifically mention "deployment" (since it can be run via wrangler setup or the autoconfig programmatic API)

#11455 d25f7e2 Thanks @dario-piotrowicz! - Fix autoconfig using absolute paths for static projects

Running the experimental autoconfig logic through wrangler setup and wrangler deploy --x-autoconfig on a static project results in absolute paths being used. This is incorrect, especially when such paths are being included in the generated wrangler.jsonc. The changes here fix the autoconfig logic to use paths relative to the project's root instead.

For example given a project located in /Users/usr/projects/sites/my-static-site, before:

// wrangler.jsonc at /Users/usr/projects/sites/my-static-site
  {
    "$schema": "node_modules/wrangler/config-schema.json",
    "name": "static",
    "compatibility_date": "2025-11-27",
    "observability": {
      "enabled": true
    },
    "assets": {
      "directory": "/Users/usr/projects/sites/my-static-site/public"
    }
  }

and after:

// wrangler.jsonc at /Users/usr/projects/sites/my-static-site
  {
    "$schema": "node_modules/wrangler/config-schema.json",
    "name": "static",
    "compatibility_date": "2025-11-27",
    "observability": {
      "enabled": true
    },
    "assets": {
      "directory": "public"
    }
  }

#11484 1cfae2d Thanks @edmundhung! - Explicitly close FileHandle in wrangler d1 execute to support Node 25
#11383 1d685cb Thanks @dario-piotrowicz! - Fix: ensure that when a remote proxy session creation fails a hard error is surfaced to the user (both in wrangler dev and in the programmatic API).

When using remote bindings, either with wrangler dev or via startRemoteProxySession/maybeStartOrUpdateRemoteProxySession the remote proxy session necessary to connect to the remote resources can fail to be created, this might happen if for example you try to set a binding with some invalid values such as:
```
MY_R2: {
	type: "r2_bucket",
	bucket_name: "non-existent", // No bucket called "non-existent" exists
	remote: true,
},
```
Before this could go undetected and cause unwanted behaviors such as requests handling hanging indefinitely, now wrangler will instead crash (or throw a hard error ion the programmatic API), clearly indicating that something went wrong during the remote session's creation.
#11366 edf896d Thanks @ascorbic! - Use correctly-formatted names when displaying detected framework details
#11461 9eaa9e2 Thanks @dario-piotrowicz! - Update the structure of the configure method of autoconfig frameworks

Update the signature of the configure function of autoconfig frameworks (AutoconfigDetails#Framework), before they would return a RawConfig object to use to update the project's wrangler config file, now they return an object that includes the RawConfig and that can potentially also hold additional data relevant to the configuration.
Updated dependencies [2b4813b, b154de2, 5ee3780, 6e63b57, 71ab562, 5e937c1]:
- miniflare@4.20251128.0
- @cloudflare/unenv-preset@2.7.12

`v4.51.0`

Compare Source

Minor Changes

#11345 d524e55 Thanks @penalosa! - Enable experimental support for autoconfig-powered Astro projects
#11228 43903a3 Thanks @petebacondarwin! - Support CLOUDFLARE_ENV environment variable for selecting the active environment

This change enables users to select the environment for commands such as CLOUDFLARE_ENV=prod wrangler versions upload. The --env command line argument takes precedence.

The CLOUDFLARE_ENV environment variable is mostly used with the @cloudflare/vite-plugin to select the environment for building the Worker to be deployed. This build also generates a "redirected deploy config" that is flattened to only contain the active environment.
To avoid accidentally deploying a version that is built for one environment to a different environment, there is an additional check to ensure that if the user specifies an environment in Wrangler it matches the original selected environment from the build.

Patch Changes

#11367 e496280 Thanks @vicb! - Rate limit r2 bulk put
Updated dependencies [4d61fae, 69f4dc3, 1133c4d, 4d61fae]:
- @cloudflare/kv-asset-handler@0.4.1
- miniflare@4.20251125.0

`v4.50.0`

Compare Source

Minor Changes

#11219 524a6e5 Thanks @Ltadrian! - Implement Hyperdrive binding TLS miniflare proxy. This will allow for wrangler dev hyperdrive bindings to connect to external
databases that require TLS.
#11233 c922a81 Thanks @emily-shen! - Add containers.unsafe to allow internal users to use additional container features

Patch Changes

#11353 0cf696d Thanks @vicb! - Use the native node:domain module when available

It is enabled when the enable_nodejs_domain_module compatibility flag is set.
#11328 bb44120 Thanks @ascorbic! - Fixes a bug that caused wrangler deploy to hang when deploying SvelteKit sites with experimental autoconfig
#11025 4a158e9 Thanks @devin-ai-integration! - Use the native node:wasi module when available

It is enabled when the enable_nodejs_wasi_module compatibility flag is set.
Updated dependencies [0cf696d, 524a6e5, 4a158e9]:
- @cloudflare/unenv-preset@2.7.11
- miniflare@4.20251118.1

`v4.49.1`

Compare Source

Patch Changes

#11344 c758809 Thanks @dario-piotrowicz! - Fix: mark the r2 bulk command as hidden and experimental
#11339 dfba912 Thanks @dario-piotrowicz! - Fix wrangler deploy erroring when it pulls down remote configs of workers containing an assets binding
Updated dependencies [e5ec8cf]:
- miniflare@4.20251118.0

`v4.49.0`

Compare Source

Minor Changes

#10703 c5c4ee5 Thanks @danlapid! - Add support for streaming tail consumers in local dev. This is an experimental new feature that allows you to register a tailStream() handler (compared to the existing tail() handler), which will receive streamed tail events from your Worker (compared to the tail() handler, which only receives batched events after your Worker has finished processing).

#11251 7035804 Thanks @penalosa! - When the WRANGLER_HIDE_BANNER environment variable is provided, Wrangler will no longer display a version banner. This applies to all commands.

For instance, previously running wrangler docs would give the following output:

> wrangler docs
 ⛅️ wrangler 4.47.0
───────────────────
Opening a link in your default browser: https://developers.cloudflare.com/workers/wrangler/commands/

With WRANGLER_HIDE_BANNER, this is now:

> WRANGLER_HIDE_BANNER=true wrangler docs
Opening a link in your default browser: https://developers.cloudflare.com/workers/wrangler/commands/

#11285 d014fa7 Thanks @vicb! - Implement the wrangler r2 bulk put bucket-name --filename list.json command.

The command uploads multiple objects to an R2 bucket.

The list of object is provided as a JSON encoded file via --filename. It is a list of key and file (respectively the name and the content for the object).
```
[
  { "key": "/path/to/obj", "file": "/path/to/file_1"},
  { "key": "/path/to/other/obj", "file": "/path/to/file_2"},
  // ...
]
```
Uploads are executed concurrently and the level of concurrency can be set via --concurrency.

The command supports the same options as wrangler r2 object put, minus --file, and --pipe and plus --concurrency
#11268 15b8460 Thanks @penalosa! - Support SvelteKit projects in autoconfig
#11258 2011b6a Thanks @dario-piotrowicz! - Add --dry-run flag to wrangler setup and also a dryRun option to runAutoConfig

Patch Changes

#11261 a352c7f Thanks @petebacondarwin! - Avoid using object lookup for OAuth Error classes
#11286 8e99766 Thanks @dario-piotrowicz! - fix: make sure that experimental_patchConfig doesn't throw if it encounters a null value
#11279 d0d3fe6 Thanks @vicb! - bump p-queue to ^9.0.0
#11278 92afbba Thanks @ascorbic! - Fixes a bug that caused .dev.vars to be ignored in OpenNext
#11244 65b4afe Thanks @petebacondarwin! - Internal refactoring to improve error traceability in wrangler dev
#11238 da8442f Thanks @jamesopstad! - Add unstable_getDurableObjectClassNameToUseSQLiteMap export. This is an internal function for use in the Vite plugin.
#11266 09cb720 Thanks @penalosa! - Use the smol-toml library for parsing TOML instead of @iarna/toml
#11236 793e2b4 Thanks @ascorbic! - Refresh expired preview tokens when running in remote dev mode
#11286 8e99766 Thanks @dario-piotrowicz! - fix: wrangler deploy failing to patch local wrangler.jsonc files if the remote tail_consumers value is null
#11275 9cbf126 Thanks @dario-piotrowicz! - Ensure that wrangler deploy run with a positional argument or with --assets does not trigger the autoconfig process (even with --experimental-autoconfig)
#11242 [dd1e560](h

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 bot added dependencies Pull requests that update a dependency file optional labels Oct 22, 2025

renovate bot changed the title ~~fix(deps): upgrade dependency hono to v4.10.2~~ fix(deps): upgrade dependency hono to v4.10.2 - autoclosed Oct 22, 2025

renovate bot closed this Oct 22, 2025

renovate bot deleted the renovate/npm-packages branch October 22, 2025 15:47

renovate bot changed the title ~~fix(deps): upgrade dependency hono to v4.10.2 - autoclosed~~ fix(deps): upgrade dependency wrangler to v4.45.0 Oct 23, 2025

renovate bot reopened this Oct 23, 2025

renovate bot force-pushed the renovate/npm-packages branch 3 times, most recently from 09b7a7b to c8e567a Compare October 28, 2025 13:39

renovate bot changed the title ~~fix(deps): upgrade dependency wrangler to v4.45.0~~ fix(deps): upgrade dependency wrangler to v4.45.1 Oct 28, 2025

renovate bot force-pushed the renovate/npm-packages branch from c8e567a to 4b6a6d6 Compare October 29, 2025 18:44

renovate bot changed the title ~~fix(deps): upgrade dependency wrangler to v4.45.1~~ fix(deps): upgrade dependency wrangler to v4.45.2 Oct 29, 2025

renovate bot force-pushed the renovate/npm-packages branch from 4b6a6d6 to 1accf23 Compare October 31, 2025 01:00

renovate bot changed the title ~~fix(deps): upgrade dependency wrangler to v4.45.2~~ fix(deps): upgrade dependency wrangler to v4.45.3 Oct 31, 2025

renovate bot force-pushed the renovate/npm-packages branch from 1accf23 to 0a44c3f Compare November 4, 2025 17:47

renovate bot changed the title ~~fix(deps): upgrade dependency wrangler to v4.45.3~~ fix(deps): upgrade dependency wrangler to v4.45.4 Nov 4, 2025

renovate bot force-pushed the renovate/npm-packages branch from 0a44c3f to e9edbfe Compare November 6, 2025 13:50

renovate bot changed the title ~~fix(deps): upgrade dependency wrangler to v4.45.4~~ fix(deps): upgrade dependency wrangler to v4.46.0 Nov 6, 2025

renovate bot force-pushed the renovate/npm-packages branch from e9edbfe to 135c95c Compare November 6, 2025 20:31

renovate bot changed the title ~~fix(deps): upgrade dependency wrangler to v4.46.0~~ fix(deps): upgrade npm packages Nov 6, 2025

renovate bot force-pushed the renovate/npm-packages branch 7 times, most recently from e93bb6a to e8af37b Compare November 14, 2025 19:12

renovate bot force-pushed the renovate/npm-packages branch 6 times, most recently from 48a489f to 75576a0 Compare November 26, 2025 15:10

renovate bot force-pushed the renovate/npm-packages branch 6 times, most recently from 2e23837 to 0324ca5 Compare December 3, 2025 17:08

renovate bot force-pushed the renovate/npm-packages branch 6 times, most recently from a5e5af5 to 3009161 Compare December 11, 2025 12:29

renovate bot force-pushed the renovate/npm-packages branch 7 times, most recently from ccf82fb to e8eb6be Compare December 19, 2025 02:04

renovate bot force-pushed the renovate/npm-packages branch 3 times, most recently from d96713a to 8fd566f Compare December 21, 2025 06:09

fix(deps): upgrade npm packages

768e9a2

renovate bot force-pushed the renovate/npm-packages branch from 8fd566f to 768e9a2 Compare December 23, 2025 05:23

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(deps): upgrade npm packages #19

fix(deps): upgrade npm packages #19

renovate bot commented Oct 22, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

fix(deps): upgrade npm packages #19

Are you sure you want to change the base?

fix(deps): upgrade npm packages #19

Conversation

renovate bot commented Oct 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Refactor

Refactor

Documentation

Refactor

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Oct 22, 2025 •

edited

Loading