chore(deps): bump the minor-and-patch group across 1 directory with 8 updates

[dependabot]

Bumps the minor-and-patch group with 8 updates in the / directory:

Package	From	To
vite-plus	0.3.0	0.3.1
@astrojs/starlight	0.41.10	0.42.0
astro	7.2.9	7.3.2
jose	6.2.10	6.2.12
@cloudflare/workers-types	5.20260830.1	5.20260908.1
wrangler	4.127.1	4.130.0
@testing-library/user-event	14.6.6	14.6.7
@cloudflare/vite-plugin	1.54.2	1.54.6

Updates vite-plus from 0.3.0 to 0.3.1

Release notes

Sourced from vite-plus's releases.

vite-plus v0.3.1: manage package-manager versions with vp env

vp env now manages Node.js and package-manager versions together. This release also fixes TanStack Start routing and stale Vitest aliases.

Breaking Changes

Package-manager setup

Vite+ replaces Corepack with managed npm, pnpm, yarn, and bun commands. It removes the corepack shim and legacy global package-manager installations (#2391), by @​liangmiQwQ.

Replace Corepack setup commands in shell profiles, CI jobs, and Dockerfiles:

Previous setup	Replacement
corepack enable	vp env setup
vp install -g pnpm@<version>	vp env default pnpm@<version>
vp install -g yarn@<version>	vp env default yarn@<version>
vp install -g bun@<version>	vp env default bun@<version>
vp install -g corepack	Use the managed package-manager commands directly

Use vp env pin <manager>@<version> to set a project version.

vp env command scope and JSON output

Unscoped vp env commands now operate on Node.js and package managers. Package managers support independent defaults, project pins, session overrides, and installation commands (#2398), by @​liangmiQwQ.

Add node to limit an operation to Node.js, for example, vp env off node or vp env unpin node. Bare versions, such as vp env default 22.19.0, still select Node.js.

Update scripts that read JSON output:

Command	New output structure
vp env current --json	node and package_manager objects
vp env list --json, vp env list-remote --json	node and package_managers groups

See the environment guide.

vp pack migration to tsdown@0.23

vp pack now uses tsdown@0.23, which removes deprecated options and changes defaults (#2614), by @​fengmk2.

1. Run vp migrate to update supported static configurations and package scripts, including projects that already use Vite+.
2. Check migration warnings in vite.config.*, tsdown.config.*, and package.json.
3. Update dynamic configurations manually. Arrays built with .map() require manual changes, even when migration reports no warning.
4. Run vp pack to check the result.

Previous option	Replacement
bundle: false	unbundle: true
outExtension	outExtensions
publicDir / --public-dir	copy / --copy

... (truncated)

Commits

• 13e1e5a release: v0.3.1: manage package-manager versions with vp env (#2623)
• 0931d9b fix(cli): share Vite runtime through the core alias (#2617)
• 3bbae42 feat(migrate): upgrade pack config for tsdown 0.23 (#2614)
• 7123545 chore(deps): update dependency voidzero-dev/setup-vp to v1.19.0 (#2619)
• b87593c fix(cli): recover from stale Vitest aliases (#2605)
• 21f6c42 ci: gate npm publishes on dependency propagation (#2601)
• 809d8b8 feat(deps): upgrade upstream dependencies (#2613)
• 585353f docs: fix Zed Oxc configuration (#2592)
• 4f97f30 feat(cli): expose dependency alignment plans (#2600)
• 03b659c feat(cli): add --quiet to vp check (#2593)
• Additional commits viewable in compare view

Updates @astrojs/starlight from 0.41.10 to 0.42.0

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.42.0

Minor Changes

• #3572 292fb17 Thanks @​HiDeoo! - Distributes package as JavaScript files with dedicated type declaration files instead of TypeScript source files.

• #4121 2623ae6 Thanks @​delucis! - Simplifies markup for Starlight’s mobile menu toggle

  ⚠️ Potentially breaking change: If you use a theme plugin, custom styles, or component overrides targeting the MobileMenuToggle button or PageFrame components, you may need to adjust these for the new markup. The button is no longer wrapped in a <starlight-menu-button> custom element and no longer uses the aria-expanded attribute. Instead, you can use the .sl-menu-button class name to target the button and the :popover-open pseudo-class to style the menu open state specifically.

  In the following example, custom styles for the menu button are updated for the new approach:

  - starlight-menu-button button {
  + .sl-menu-button {
    color: var(--sl-color-text);
  }
  
  starlight-menu-button[aria-expanded='true'] button {
  
  
  .sl-menu-button:has(~ :popover-open) {
  color: var(--sl-color-text-accent-high);
  }

See MobileMenuToggle.astro and PageFrame.astro on GitHub for the full source code of the updated components.

#3572 292fb17 Thanks @​HiDeoo! - Removes the tagline configuration option, which was never used.

If your configuration included a tagline option, you can safely remove it without any replacement.

#4134 6135f01 Thanks @​HiDeoo! - Updates internal @astrojs/mdx, @astrojs/markdown-satteri, and satteri dependencies.

⚠️ BREAKING CHANGE: The following minimum versions are now required:

• astro v7.2.10 or later
• @astrojs/markdown-satteri 0.4.0 or later (if you use it)
• @astrojs/markdown-remark 7.3.0 or later (if you use it)

Please update Starlight and Astro together:

npx @astrojs/upgrade

#4121 2623ae6 Thanks @​delucis! - Refactors Starlight’s mobile menu toggle to work when JavaScript fails or is disabled

⚠️ BREAKING CHANGE: This release drops official support for Chromium-based browsers prior to version 116 (released August 2023), Safari-based browsers prior to version 17.0 (released September 2023), and Firefox prior to version 125 (released April 2024). You can find a list of currently supported browsers and their versions using this browserslist query.

This change also removes the data-mobile-menu-expanded attribute, which was previously added to <body> while the mobile menu is open. If you have custom code that was depending on this attribute, you will need to update it to use a new selector to check if the mobile menu is open.

In the following example, a custom background colour for the site header while the menu is open is updated for the new approach:

... (truncated)

Changelog

Sourced from @​astrojs/starlight's changelog.

0.42.0

Minor Changes

• #3572 292fb17 Thanks @​HiDeoo! - Distributes package as JavaScript files with dedicated type declaration files instead of TypeScript source files.

• #4121 2623ae6 Thanks @​delucis! - Simplifies markup for Starlight’s mobile menu toggle

  ⚠️ Potentially breaking change: If you use a theme plugin, custom styles, or component overrides targeting the MobileMenuToggle button or PageFrame components, you may need to adjust these for the new markup. The button is no longer wrapped in a <starlight-menu-button> custom element and no longer uses the aria-expanded attribute. Instead, you can use the .sl-menu-button class name to target the button and the :popover-open pseudo-class to style the menu open state specifically.

  In the following example, custom styles for the menu button are updated for the new approach:

  - starlight-menu-button button {
  + .sl-menu-button {
    color: var(--sl-color-text);
  }
  
  starlight-menu-button[aria-expanded='true'] button {
  
  
  .sl-menu-button:has(~ :popover-open) {
  color: var(--sl-color-text-accent-high);
  }

See MobileMenuToggle.astro and PageFrame.astro on GitHub for the full source code of the updated components.

#3572 292fb17 Thanks @​HiDeoo! - Removes the tagline configuration option, which was never used.

If your configuration included a tagline option, you can safely remove it without any replacement.

#4134 6135f01 Thanks @​HiDeoo! - Updates internal @astrojs/mdx, @astrojs/markdown-satteri, and satteri dependencies.

⚠️ BREAKING CHANGE: The following minimum versions are now required:

• astro v7.2.10 or later
• @astrojs/markdown-satteri 0.4.0 or later (if you use it)
• @astrojs/markdown-remark 7.3.0 or later (if you use it)

Please update Starlight and Astro together:

npx @astrojs/upgrade

#4121 2623ae6 Thanks @​delucis! - Refactors Starlight’s mobile menu toggle to work when JavaScript fails or is disabled

⚠️ BREAKING CHANGE: This release drops official support for Chromium-based browsers prior to version 116 (released August 2023), Safari-based browsers prior to version 17.0 (released September 2023), and Firefox prior to version 125 (released April 2024). You can find a list of currently supported browsers and their versions using this browserslist query.

This change also removes the data-mobile-menu-expanded attribute, which was previously added to <body> while the mobile menu is open. If you have custom code that was depending on this attribute, you will need to update it to use a new selector to check if the mobile menu is open.

... (truncated)

Commits

• 88ad3c2 [ci] release (#4172)
• 74cb3f1 Update dependencies (#4173)
• 6135f01 Use Sätteri 0.10 APIs (#4134)
• 2623ae6 Refactor mobile menu to use Popover API (#4121)
• 09af1c6 chore(deps): update magic-string to v1 (#4082)
• 292fb17 [i18nIgnore] Transpile Starlight packages (#3572)
• 0138f22 [ci] release (#4169)
• 32a5e29 Fix hidden heading anchor links (#4167)
• cdfafd8 perf: optimize route and sidebar lookups (#4148)
• dd7fb97 chore: add benchmarks (#4157)
• See full diff in compare view

Updates astro from 7.2.9 to 7.3.2

Release notes

Sourced from astro's releases.

astro@7.3.2

Patch Changes

• #17896 a548223 Thanks @​matthewp! - Fixes <script>/<style> rendering in MDX so that only literal content (including content injected by remark/rehype plugins) is treated as trusted markup. A dynamic value passed as a <script>/<style> child (e.g. <script>{value}</script>) is now escaped like any other element's content instead of being rendered raw. Use set:html to explicitly opt a dynamic value back into raw rendering.

• #17931 c1a6a89 Thanks @​astro-factory! - Fixes the dev toolbar returning a 504 "Outdated Optimize Dep" error when a workspace-linked package imports a dependency that Vite's initial scan did not discover

• #17908 42e9188 Thanks @​astro-factory! - Fixes i18n fallback routing replacing the first substring match instead of the actual locale segment, which mangled paths like /energy/en/about into /esergy/en/about

• #17936 4b92ddc Thanks @​astro-factory! - Fixes sessions breaking in dev mode with the Cloudflare adapter when middleware is present

• Updated dependencies [a548223]:

  • @​astrojs/markdown-satteri@​0.4.1

astro@7.3.1

Patch Changes

• #17899 0389640 Thanks @​ematipico! - Fixes an error that prevented projects using astro:assets from starting or building

astro@7.3.0

Minor Changes

• #17767 ce7c91f Thanks @​astro-factory! - Adds --ignore-lock flag to astro preview, allowing multiple preview servers to run simultaneously on different ports. This is useful for E2E testing workflows (e.g., Playwright) that need to run several preview servers at once.

• #17818 c0b6581 Thanks @​florian-lefebvre! - Adds a logger parameter to image services hooks

  Custom image services now receive Astro's runtime logger as an extra argument. Messages logged with it are routed through the destination configured in logger and respect your log level, instead of being written straight to the console:

  import type { LocalImageService } from 'astro';
  const service: LocalImageService = {
  // ...
  async transform(inputBuffer, transform, imageConfig, logger) {
  logger.warn(Could not optimize "${transform.src}". Passing it through unchanged.);
  return { data: inputBuffer, format: 'png' };
  },
  };

  Astro's built-in Sharp service now uses this logger for the warnings it emits when it encounters an unexpected or unsupported source format.

• #17818 c0b6581 Thanks @​florian-lefebvre! - Adds logger to the context object passed to cache providers

  Custom cache providers now receive Astro's runtime logger on the context passed to onRequest(). Messages logged with it are routed through the destination configured in logger and respect your log level, instead of being written straight to the console:

  import type { CacheProvider } from 'astro';
  const provider: CacheProvider = {

... (truncated)

Changelog

Sourced from astro's changelog.

7.3.2

Patch Changes

• #17896 a548223 Thanks @​matthewp! - Fixes <script>/<style> rendering in MDX so that only literal content (including content injected by remark/rehype plugins) is treated as trusted markup. A dynamic value passed as a <script>/<style> child (e.g. <script>{value}</script>) is now escaped like any other element's content instead of being rendered raw. Use set:html to explicitly opt a dynamic value back into raw rendering.

• #17931 c1a6a89 Thanks @​astro-factory! - Fixes the dev toolbar returning a 504 "Outdated Optimize Dep" error when a workspace-linked package imports a dependency that Vite's initial scan did not discover

• #17908 42e9188 Thanks @​astro-factory! - Fixes i18n fallback routing replacing the first substring match instead of the actual locale segment, which mangled paths like /energy/en/about into /esergy/en/about

• #17936 4b92ddc Thanks @​astro-factory! - Fixes sessions breaking in dev mode with the Cloudflare adapter when middleware is present

• Updated dependencies [a548223]:

  • @​astrojs/markdown-satteri@​0.4.1

7.3.1

Patch Changes

• #17899 0389640 Thanks @​ematipico! - Fixes an error that prevented projects using astro:assets from starting or building

7.3.0

Minor Changes

• #17767 ce7c91f Thanks @​astro-factory! - Adds --ignore-lock flag to astro preview, allowing multiple preview servers to run simultaneously on different ports. This is useful for E2E testing workflows (e.g., Playwright) that need to run several preview servers at once.

• #17818 c0b6581 Thanks @​florian-lefebvre! - Adds a logger parameter to image services hooks

  Custom image services now receive Astro's runtime logger as an extra argument. Messages logged with it are routed through the destination configured in logger and respect your log level, instead of being written straight to the console:

  import type { LocalImageService } from 'astro';
  const service: LocalImageService = {
  // ...
  async transform(inputBuffer, transform, imageConfig, logger) {
  logger.warn(Could not optimize "${transform.src}". Passing it through unchanged.);
  return { data: inputBuffer, format: 'png' };
  },
  };

  Astro's built-in Sharp service now uses this logger for the warnings it emits when it encounters an unexpected or unsupported source format.

• #17818 c0b6581 Thanks @​florian-lefebvre! - Adds logger to the context object passed to cache providers

  Custom cache providers now receive Astro's runtime logger on the context passed to onRequest(). Messages logged with it are routed through the destination configured in logger and respect your log level, instead of being written straight to the console:

... (truncated)

Commits

• aa4949e [ci] release (#17915)
• 42e9188 fix(i18n): replace locale segment by index in fallback routing (#17907) (#17908)
• 4b92ddc Guard setFetchHandler call in non-runnable dev entrypoint to fix sessions + m...
• c1a6a89 fix: include .astro files in client optimizeDeps entries to prevent 504 on la...
• a548223 Only treat literal script/style content as raw in MDX rendering (#17896)
• 92f23cc [ci] release (#17900)
• 0389640 fix: dont use internal paths (#17899)
• f800de1 [ci] release (#17881)
• 1e0b7e6 [ci] format
• 4671a5c chore(deps): update react to v19 in 0-css fixture (#17888)
• Additional commits viewable in compare view

Updates jose from 6.2.10 to 6.2.12

Release notes

Sourced from jose's releases.

v6.2.12

Documentation

• clarify and shorten public API guidance (be62530)

Refactor

• simplify JWS and JWE operation cores (92e9640)

Performance

• avoid copying AES-GCM output (6925d43)
• deduplicate pending jwks key imports (bf5138b)
• encode single-signature JWS input once (7bc9a33)
• normalize General JWE shared headers once (78637bd)
• normalize jwks selection metadata once (fd3ae3f)
• use native encoding for larger ASCII strings (b23a6f3)

v6.2.11

Documentation

• render subpath indexes as tables (94589ee)
• shorten API index descriptions (681482f)

Refactor

• model JWE key management modes (e01dda6)
• types: reduce declaration repetition (55b970f)

Changelog

Sourced from jose's changelog.

6.2.12 (2026-09-05)

Documentation

• clarify and shorten public API guidance (be62530)

Refactor

• simplify JWS and JWE operation cores (92e9640)

Performance

• avoid copying AES-GCM output (6925d43)
• deduplicate pending jwks key imports (bf5138b)
• encode single-signature JWS input once (7bc9a33)
• normalize General JWE shared headers once (78637bd)
• normalize jwks selection metadata once (fd3ae3f)
• use native encoding for larger ASCII strings (b23a6f3)

6.2.11 (2026-09-04)

Documentation

• render subpath indexes as tables (94589ee)
• shorten API index descriptions (681482f)

Refactor

• model JWE key management modes (e01dda6)
• types: reduce declaration repetition (55b970f)

Commits

• 505a55b chore(release): 6.2.12
• 7bc9a33 perf: encode single-signature JWS input once
• 78637bd perf: normalize General JWE shared headers once
• bf5138b perf: deduplicate pending jwks key imports
• b23a6f3 perf: use native encoding for larger ASCII strings
• fd3ae3f perf: normalize jwks selection metadata once
• 6925d43 perf: avoid copying AES-GCM output
• be62530 docs: clarify and shorten public API guidance
• 1b41312 build: preserve README when generation fails
• 0b51829 build: check tree-shaking for every public binding
• Additional commits viewable in compare view

Updates @cloudflare/workers-types from 5.20260830.1 to 5.20260908.1

Commits

• See full diff in compare view

Updates wrangler from 4.127.1 to 4.130.0

Release notes

Sourced from wrangler's releases.

wrangler@4.130.0

Minor Changes

• #14372 dbf6aad Thanks @​ichernetsky-cf! - Add containers[].observability support to wrangler deploy

  Wrangler now accepts container-specific observability settings via containers[].observability, including application-level targeting fields for Containers. Root observability continues to work as a fallback when a container does not define its own observability settings.

  wrangler deploy now preserves legacy configuration.observability for existing container apps that still use rollout-based observability, while using top-level application observability for new or already-migrated apps.

  Existing application diffs are now normalized even when stored resource limits cannot be mapped to a named instance type. API-only metadata and equivalent managed-registry image names no longer appear as edits or affect whether deployment changes require a rollout.

• #15004 e20df20 Thanks @​MattieTK! - Delegate agent Pages project creation with a production branch to Workers

  When run by an AI agent, wrangler pages project create --production-branch <name> is now eligible for delegation to a Workers static-assets deploy. The production branch names the target that a Workers deploy would publish to, so it does not need to disqualify a brand-new project from delegation.

  wrangler pages deploy --branch <name> remains on Pages because an interactive new-project flow separately prompts for its production branch. The deployment branch may therefore represent a preview and cannot safely be converted into a production Workers deployment.

• #15004 e20df20 Thanks @​MattieTK! - Widen agent Pages-to-Workers delegation to new projects on accounts that already use Pages

  When run by an AI agent, wrangler pages deploy and wrangler pages project create now delegate a brand-new static Pages project to a Workers static-assets deploy even when the account already has other Pages projects. The gate is now per-project rather than per-account: a command targeting a project that already exists stays on Pages, but a new project is delegated regardless of the account's other Pages projects.

  A project name restored from the Pages configuration cache is only used when the cache belongs to the currently authenticated account. An account-matching cached name remains on Pages even when the project is missing remotely, preserving the user's recorded Pages intent. After switching accounts, an otherwise unnamed deploy stays on Pages rather than treating a stale cached project name as a new project on the selected account.

Patch Changes

• #15560 edb3631 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  @​cloudflare/workers-types	^5.20260907.1	^5.20260908.1
  workerd	1.20260907.1	1.20260908.1

• #15557 63c7ff1 Thanks @​tomekancu! - Fix wrangler d1 execute --local being extremely slow with large SQL files or commands

  The local SQL splitter consumed quoted strings and comments character-by-character, re-checking the full accumulated string each time. This made splitting a large quoted value or comment quadratic, so seed files could take tens of seconds to run. The splitter now only inspects a bounded trailing window on each step, making splitting effectively linear. The remote path is unaffected as it imports the file server-side.

• #15542 a4e41df Thanks @​NAVEENKUMARKR777! - Fix wrangler dev running the custom build command twice on startup and on every config change

  Wrangler already runs the custom build.command once before starting wrangler dev, to resolve the Worker's entry point. When dev.watch wasn't explicitly disabled, BundlerController then unconditionally ran the same build command again the moment it started watching for changes, and repeated this on every subsequent config reload too.

  For fast build commands this just meant duplicate log output (e.g. a vite build visibly running twice at startup). For slower or stateful build commands, running two builds concurrently against the same output files could corrupt the result or fail outright (for example, non-deterministic wasm-opt failures have been reported for Rust builds).

  The initial watcher setup now only bundles the output the build command already produced, instead of re-running the command. Real file changes detected by the watcher still re-run the build command as before.

• Updated dependencies [edb3631, bcebf08]:

  • miniflare@5.20260908.0-alpha

wrangler@4.129.1

... (truncated)

Commits

• 5705262 Version Packages (#15555)
• dbf6aad Add containers[].observability support to wrangler deploy (#14372)
• e20df20 [wrangler] Widen agent Pages-to-Workers delegation for new projects (#15004)
• 63c7ff1 Fix wrangler d1 execute performance for local (#15557)
• 9c60d14 Enable referencing Worker configs directly in cross-Worker bindings (#15511)
• a849e0d [workers-utils] Share named tunnel resolution (#15470)
• a4e41df [wrangler] Fix wrangler dev running the custom build command twice (#15542)
• 87fd28c Revert "graduate miniflare v5" (#15551)
• 7f14caa Version Packages (#15510)
• 411dbc4 Revert "fix(wrangler): tolerate missing KV access when deleting Workers" (#15...
• Additional commits viewable in compare view

Updates @testing-library/user-event from 14.6.6 to 14.6.7

Release notes

Sourced from @​testing-library/user-event's releases.

v14.6.7

14.6.7 (2026-09-02)

Bug Fixes

• normalize DataTransfer format aliases (#1326) (1e0020b)
• feature: Add iframe support for user.keyboard typing (#1275) (1e0020b)

Commits

• 1e0020b fix: normalize DataTransfer format aliases (#1326)
• d4b0593 feature: Add iframe support for user.keyboard typing (#1275)
• See full diff in compare view

Updates @cloudflare/vite-plugin from 1.54.2 to 1.54.6

Release notes

Sourced from @​cloudflare/vite-plugin's releases.

@​cloudflare/vite-plugin@​1.54.6

Patch Changes

• Updated dependencies [edb3631, dbf6aad, bcebf08, e20df20, e20df20, 63c7ff1, a4e41df]:
  • miniflare@5.20260908.0-alpha
  • wrangler@4.130.0

@​cloudflare/vite-plugin@​1.54.5

Patch Changes

• #15519 e004845 Thanks @​devaniketh! - Preserve HTTP/2 :authority header and non-default port in dev server requests

  When Vite runs over HTTPS with HTTP/2 enabled, browsers send authority via the :authority pseudo-header rather than Host. Previously, pseudo-headers were omitted when creating Fetch requests, causing non-default ports to be dropped from request.url and X-Forwarded-Host. Authority and scheme are now preserved from HTTP/2 pseudo-headers and request properties.

• Updated dependencies [8bbcb9f, 2b42d6f, ea5634e, c0c6504, ffc7efd, 682cd44]:

  • miniflare@5.20260907.0-alpha
  • wrangler@4.129.1

@​cloudflare/vite-plugin@​1.54.4

Patch Changes

• #15407 7662118 Thanks @​xgame92! - Surface Worker export type fetch errors during development

  The Vite plugin now reports the Worker name, HTTP status, and response body when fetching export types fails. This preserves the underlying error instead of replacing it with a JSON parsing error.

• Updated dependencies [00a9f2f, 1dba24a, d40a634, 7c1b2a6, 93d72a5, f6fb347, f6fb347, dc24057, d2d8eea]:

  • miniflare@5.20260903.0-alpha
  • wrangler@4.129.0

@​cloudflare/vite-plugin@​1.54.3

Patch Changes

• Updated dependencies [dbbb795, 200780f, b3f2628, 87a7acf, 1809c5e, ea28cc3, b3fb2bf, 707cb6f]:
  • wrangler@4.128.0
  • miniflare@5.20260831.0-alpha

Changelog

Sourced from @​cloudflare/vite-plugin's changelog.

1.54.6

Patch Changes

• Updated dependencies [edb3631, dbf6aad, bcebf08, e20df20, e20df20, 63c7ff1, a4e41df]:
  • miniflare@5.20260908.0-alpha
  • wrangler@4.130.0

1.54.5

Patch Changes

• #15519 e004845 Thanks @​devaniketh! - Preserve HTTP/2 :authority header and non-default port in dev server requests

  When Vite runs over HTTPS with HTTP/2 enabled, browsers send authority via the :authority pseudo-header rather than Host. Previously, pseudo-headers were omitted when creating Fetch requests, causing non-default ports to be dropped from request.url and X-Forwarded-Host. Authority and scheme are now preserved from HTTP/2 pseudo-headers and request properties.

• Updated dependencies [8bbcb9f, 2b42d6f, ea5634e, c0c6504, ffc7efd, 682cd44]:

  • miniflare@5.20260907.0-alpha
  • wrangler@4.129.1

1.54.4

Patch Changes

• #15407 7662118 Thanks @​xgame92! - Surface Worker export type fetch errors during development

  The Vite plugin now reports the Worker name, HTTP status, and response body when fetching export types fails. This preserves the underlying error instead of replacing it with a JSON parsing error.

• Updated dependencies [00a9f2f, 1dba24a, d40a634, 7c1b2a6, 93d72a5, f6fb347, f6fb347, dc24057, d2d8eea]:

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	nyuchi-docs-mcp	28c5d46	Sep 11 2026, 07:01 PM

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	shamwari-docs-ai	28c5d46	Sep 11 2026, 07:01 PM

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	nyuchi-docs	28c5d46	Commit Preview URL Branch Preview URL	Sep 11 2026, 07:01 PM