chore(deps): bump the dependencies group across 1 directory with 15 updates

[dependabot]

Bumps the dependencies group with 15 updates in the / directory:

Package	From	To
@fontsource-variable/geist	5.2.9	5.3.0
@llamaindex/llama-cloud	2.11.0	2.12.0
@tanstack/react-query	5.101.2	5.101.4
@tanstack/react-start	1.168.30	1.168.32
posthog-js	1.404.1	1.406.2
posthog-node	5.45.2	5.46.0
radix-ui	1.6.2	1.6.3
react	19.2.7	19.2.8
react-dom	19.2.7	19.2.8
@cloudflare/vite-plugin	1.45.1	1.46.0
@cloudflare/vitest-pool-workers	0.18.6	0.18.7
@types/node	22.20.1	26.1.1
typescript	6.0.3	7.0.2
wrangler	4.112.0	4.113.0
@cloudflare/workers-types	5.20260721.1	5.20260722.1

Updates @fontsource-variable/geist from 5.2.9 to 5.3.0

Commits

• See full diff in compare view

Updates @llamaindex/llama-cloud from 2.11.0 to 2.12.0

Release notes

Sourced from @​llamaindex/llama-cloud's releases.

v2.12.0

2.12.0 (2026-07-21)

Features

• brokered-connection: wire data-source create/read to brokered_connection_id (#21699) (92df958)
• gdrive: reuse-first connection picker in the data-source connect modal (#21725) (4139205)
• llamaparse: agentic 2026-07-15 — Markdown-pipe table body for Gemini 3.1 Flash-Lite (EU primary) (#22208) (19c059a)
• parse: adding forms pass to api layer (forms=enrich param + output types) (#22012) (4a52e97)
• parse: confidence_scores="verified" — per-page AI-verified confidence + document-level score (#22083) (239f9f3)
• parse: rename confidence scoring option + billing event (confidence_score_effort / confidence_score_high) (#22290) (49059bf)
• sdk: drop the prod project suffix from Go and Java namespaces (3fb3bed)
• extract: GA agentic_plus tier

Bug Fixes

• parse: declare the recursive form node schemas as models (fe0a9a4)

Changelog

Sourced from @​llamaindex/llama-cloud's changelog.

2.12.0 (2026-07-21)

Features

• brokered-connection: wire data-source create/read to brokered_connection_id (#21699) (92df958)
• gdrive: reuse-first connection picker in the data-source connect modal (#21725) (4139205)
• llamaparse: agentic 2026-07-15 — Markdown-pipe table body for Gemini 3.1 Flash-Lite (EU primary) (#22208) (19c059a)
• parse: adding forms pass to api layer (forms=enrich param + output types) (#22012) (4a52e97)
• parse: confidence_scores="verified" — per-page AI-verified confidence + document-level score (#22083) (239f9f3)
• parse: rename confidence scoring option + billing event (confidence_score_effort / confidence_score_high) (#22290) (49059bf)
• sdk: drop the prod project suffix from Go and Java namespaces (3fb3bed)

Bug Fixes

• parse: declare the recursive form node schemas as models (fe0a9a4)

Commits

• 84343b5 Merge pull request #86 from run-llama/release-please--branches--main--compone...
• a9cf7c5 release: 2.12.0
• 3f524b0 Merge pull request #85 from run-llama/stainless/release
• 3fb3bed feat(sdk): drop the prod project suffix from Go and Java namespaces
• ab8731e GA the agentic_plus extract tier (#22275)
• 49059bf feat(parse): rename confidence scoring option + billing event (confidence_sco...
• 19c059a feat(llamaparse): agentic 2026-07-15 — Markdown-pipe table body for Gemini 3....
• fe0a9a4 fix(parse): declare the recursive form node schemas as models
• 239f9f3 feat(parse): confidence_scores="verified" — per-page AI-verified confidence +...
• 4a52e97 feat(parse): adding forms pass to api layer (forms=enrich param + output ty...
• Additional commits viewable in compare view

Updates @tanstack/react-query from 5.101.2 to 5.101.4

Release notes

Sourced from @​tanstack/react-query's releases.

@​tanstack/react-query-devtools@​5.101.4

Patch Changes

• Updated dependencies []:
  • @​tanstack/query-devtools@​5.101.4
  • @​tanstack/react-query@​5.101.4

@​tanstack/react-query-next-experimental@​5.101.4

Patch Changes

• Updated dependencies []:
  • @​tanstack/react-query@​5.101.4

@​tanstack/react-query-persist-client@​5.101.4

Patch Changes

• Updated dependencies []:
  • @​tanstack/query-persist-client-core@​5.101.4
  • @​tanstack/react-query@​5.101.4

@​tanstack/react-query@​5.101.4

Patch Changes

• Updated dependencies []:
  • @​tanstack/query-core@​5.101.4

@​tanstack/react-query-devtools@​5.101.3

Patch Changes

• Updated dependencies []:
  • @​tanstack/query-devtools@​5.101.3
  • @​tanstack/react-query@​5.101.3

@​tanstack/react-query-next-experimental@​5.101.3

Patch Changes

• Updated dependencies []:
  • @​tanstack/react-query@​5.101.3

@​tanstack/react-query-persist-client@​5.101.3

Patch Changes

• Updated dependencies []:
  • @​tanstack/query-persist-client-core@​5.101.3
  • @​tanstack/react-query@​5.101.3

@​tanstack/react-query@​5.101.3

Patch Changes

• Updated dependencies [7e3c822]:

... (truncated)

Changelog

Sourced from @​tanstack/react-query's changelog.

5.101.4

Patch Changes

• Updated dependencies []:
  • @​tanstack/query-core@​5.101.4

5.101.3

Patch Changes

• Updated dependencies [7e3c822]:
  • @​tanstack/query-core@​5.101.3

Commits

• 86bb8a6 ci: Version Packages (#11094)
• 181ea82 ci: Version Packages (#11089)
• 6d55b07 test({react,preact}-query): use the '.then()' convention consistently (#11085)
• 44f38df test({react,preact,solid}-query/useInfiniteQuery): inline the shared 'fetchIt...
• d1558c1 test({react,preact}-query/usePrefetchQuery): inline the 'generateQueryFn' fac...
• 99690d1 test({react,preact}-query/usePrefetchInfiniteQuery): inline single-use helper...
• 10770f0 test({react,preact}-query/usePrefetchInfiniteQuery): inline the shared 'Suspe...
• dbd5a86 test({react,preact}-query/usePrefetchQuery): inline the shared 'Suspended' co...
• b955f60 test({react,preact}-query/useSuspenseQuery): assert the 'loading' fallback is...
• b9c657e test({react,preact}-query/usePrefetchQuery): assert the 'Loading...' fallback...
• Additional commits viewable in compare view

Updates @tanstack/react-start from 1.168.30 to 1.168.32

Release notes

Sourced from @​tanstack/react-start's releases.

@​tanstack/react-start@​1.168.32

Patch Changes

• Updated dependencies []:
  • @​tanstack/start-plugin-core@​1.171.24
  • @​tanstack/react-start-rsc@​0.1.31

@​tanstack/react-start@​1.168.31

Patch Changes

• Updated dependencies [ffdd64e]:
  • @​tanstack/start-plugin-core@​1.171.23
  • @​tanstack/react-start-rsc@​0.1.30

Changelog

Sourced from @​tanstack/react-start's changelog.

1.168.32

Patch Changes

• Updated dependencies []:
  • @​tanstack/start-plugin-core@​1.171.24
  • @​tanstack/react-start-rsc@​0.1.31

1.168.31

Patch Changes

• Updated dependencies [ffdd64e]:
  • @​tanstack/start-plugin-core@​1.171.23
  • @​tanstack/react-start-rsc@​0.1.30

Commits

• 49bd9fa ci: Version Packages (#7857)
• ecb1ef4 ci: Version Packages (#7854)
• See full diff in compare view

Updates posthog-js from 1.404.1 to 1.406.2

Release notes

Sourced from posthog-js's releases.

posthog-js@1.406.2

1.406.2

Patch Changes

• #4206 a3112d9 Thanks @​posthog! - fix(surveys): stop recurring surveys re-showing off a stale internal targeting flag

  Recurring surveys could re-display and record a duplicate response when the eligibility check ran against a cached internal targeting flag before fresh flags had loaded. The display loop now waits for feature flags to actually load before trusting the internal targeting flag, and forces a flag reload after a survey is completed so the flag recomputes promptly. (2026-07-21)

posthog-js@1.406.1

1.406.1

Patch Changes

• #4127 220fa2c Thanks @​sarmah-rup! - Don't let save_referrer overwrite a $referrer / $referring_domain that was explicitly set via posthog.register(), so registered attribution values survive pageviews in SPA and iframe contexts (2026-07-21)

posthog-js@1.406.0

1.406.0

Minor Changes

• #4194 d39b903 Thanks @​dustinbyrne! - Move shared browser utility implementations into @posthog/browser-common and consume them directly from posthog-js. (2026-07-21)

Patch Changes

• #4204 ba977d0 Thanks @​turnipdabeets! - Keep autocapture off when a remote config response omits autocapture_opt_out. The SDK now retains the last known server value for the missing-field case, the same as when the config fetch fails, instead of enabling autocapture. Values persisted by earlier SDK versions are still trusted; a browser holding a stale value corrects itself on the first config response that includes the field. (2026-07-21)
• Updated dependencies [d39b903]:
  • @​posthog/browser-common@​0.2.0

posthog-js@1.405.3

1.405.3

Patch Changes

• #4200 91505ba Thanks @​pauldambra! - fix: apply the active full snapshot interval as soon as a recording trigger matches (2026-07-21)

posthog-js@1.405.2

1.405.2

Patch Changes

• #4198 fbfc84f Thanks @​pauldambra! - feat: make the pending session recording trigger buffer interval configurable

... (truncated)

Commits

• 4f49b55 chore: update versions and lockfile [version bump]
• a3112d9 fix(surveys): stop recurring surveys re-showing off a stale internal targetin...
• 975bd48 chore: update versions and lockfile [version bump]
• 220fa2c fix: don't overwrite registered $referrer with document.referrer (#4127)
• 9df5cc0 docs(browser): use customizations entrypoint in playgrounds (#4212)
• 32fb42b chore: update versions and lockfile [version bump]
• ba977d0 fix: ignore missing autocapture_opt_out in remote config instead of enabling ...
• d39b903 refactor(browser): move shared utilities to browser-common (#4194)
• 9c76008 chore: update versions and lockfile [version bump]
• 91505ba fix: reschedule replay snapshots after trigger activation (#4200)
• Additional commits viewable in compare view

Updates posthog-node from 5.45.2 to 5.46.0

Release notes

Sourced from posthog-node's releases.

posthog-node@5.46.0

5.46.0

Minor Changes

• #4172 9621830 Thanks @​haacked! - send minimal $feature_flag_called events when the server enables it

  When the v2 /flags response carries minimalFlagCalledEvents: true (or, for posthog-node local evaluation, the flag-definitions payload carries minimal_flag_called_events: true) and the evaluated flag is not linked to an experiment ($feature_flag_has_experiment === false), $feature_flag_called events are rebuilt from a strict allowlist of flag-evaluation, processing-control, and SDK-identity properties. Super properties, $set/$set_once, the $feature/<key> enumeration, $active_feature_flags, and the context envelope are stripped. Any missing signal (no gate on the response, bootstrapped or locally injected flags, has_experiment unknown) falls back to the full event, and experiment-linked flags always send the full envelope. The gate is stored alongside the cached flags (posthog-js persistence, posthog-node poller state) and is server-controlled, with no SDK-side configuration. before_send runs after the filter and may re-add stripped properties. (2026-07-20)

Patch Changes

• Updated dependencies [9621830]:
  • @​posthog/core@​1.44.0

Changelog

Sourced from posthog-node's changelog.

5.46.0

Minor Changes

• #4172 9621830 Thanks @​haacked! - send minimal $feature_flag_called events when the server enables it

  When the v2 /flags response carries minimalFlagCalledEvents: true (or, for posthog-node local evaluation, the flag-definitions payload carries minimal_flag_called_events: true) and the evaluated flag is not linked to an experiment ($feature_flag_has_experiment === false), $feature_flag_called events are rebuilt from a strict allowlist of flag-evaluation, processing-control, and SDK-identity properties. Super properties, $set/$set_once, the $feature/<key> enumeration, $active_feature_flags, and the context envelope are stripped. Any missing signal (no gate on the response, bootstrapped or locally injected flags, has_experiment unknown) falls back to the full event, and experiment-linked flags always send the full envelope. The gate is stored alongside the cached flags (posthog-js persistence, posthog-node poller state) and is server-controlled, with no SDK-side configuration. before_send runs after the filter and may re-add stripped properties. (2026-07-20)

Patch Changes

• Updated dependencies [9621830]:
  • @​posthog/core@​1.44.0

Commits

• 34a03e2 chore: update versions and lockfile [version bump]
• 9621830 feat(flags): minimize $feature_flag_called events for non-experiment flags (#...
• 8bf1b19 chore: ban object-literal type assertions in package sources (#4192)
• See full diff in compare view

Updates radix-ui from 1.6.2 to 1.6.3

Changelog

Sourced from radix-ui's changelog.

1.6.3

Dialog

• Fixed broken ARIA references in Dialogs where title or description elements are not rendered.

Slider

• Fixed a bug where onValueCommit was not called when a slider thumb was dragged across another thumb.

Toast

• Fixed Toast removing non-focused toasts when pressing Escape.

Tooltip

• Fixed a bug where Tooltip.Content children were mounted to the DOM twice.

Other updates

• Fixed overriding inline animation style in Popper.Content.
• Improved tree-shaking so bundlers can drop unused components. Component parts are now marked /* @__PURE__ */ and use named render functions instead of Component.displayName = ... assignments, which previously prevented dead-code elimination with some bundlers.
• Widened virtualRef prop type to allow RefObject<Measurable | null> in popover components.
• Fixed dev-only checks with conditional exports to drop dev-warnings from production builds.
• Added per-primitive subpath entry points so each primitive can be imported directly, eg. import { Accordion } from 'radix-ui/accordion' or import * as Accordion from 'radix-ui/accordion'. This mirrors the namespaced exports available from the root radix-ui entry point.
• Fixed a bug where updating a Checkbox, Switch, or RadioGroup value programmatically (eg. a "select all" control) while inside a <form> would dispatch a click event from the hidden bubble input that propagated to ancestor onClick handlers.

Commits

• See full diff in compare view

Updates react from 19.2.7 to 19.2.8

Release notes

Sourced from react's releases.

19.2.8 (July 21st, 2026)

React Server Components

• Performance improvements when decoding (#37087 by @​eps1lon)

Commits

• 1dd4ecb [FlightReply] Performance improvements when decoding (#37087)
• b0d2fdb [19.2.x] Update required references to GitHub repo (#36753)
• See full diff in compare view

Updates react-dom from 19.2.7 to 19.2.8

Release notes

Sourced from react-dom's releases.

19.2.8 (July 21st, 2026)

React Server Components

• Performance improvements when decoding (#37087 by @​eps1lon)

Commits

• 1dd4ecb [FlightReply] Performance improvements when decoding (#37087)
• b0d2fdb [19.2.x] Update required references to GitHub repo (#36753)
• See full diff in compare view

Updates @cloudflare/vite-plugin from 1.45.1 to 1.46.0

Release notes

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

@​cloudflare/vite-plugin@​1.46.0

Minor Changes

• #14724 a50f73a Thanks @​jamesopstad! - Add a settings export to the experimental cloudflare.config.ts config

  Account-level settings (accountId, complianceRegion) now live in a dedicated, named settings export authored via defineSettings, rather than on the Worker config. A cloudflare.config.ts can export at most one settings object; the Worker itself is the default export.

  // cloudflare.config.ts
  import { defineSettings, defineWorker } from "wrangler/experimental-config";
  import * as entrypoint from "./src/index.ts" with { type: "cf-worker" };
  export const settings = defineSettings({
  accountId: "<your-account-id>",
  });
  export default defineWorker({
  name: "my-worker",
  entrypoint,
  compatibilityDate: "2026-05-18",
  });

  This is only used behind the experimental new-config path (wrangler --experimental-new-config and the @cloudflare/vite-plugin experimental.newConfig option).

Patch Changes

• Updated dependencies [42af66d, a0a091b, f03b108, deae171, 0df3d43, d83a476, 4e92e32, d1d6945, 4815711, a0c8bb1, a50f73a, 2b390d7, c82d96b, 34430b3, f75ae5d]:
  • miniflare@4.20260721.0
  • wrangler@4.113.0

Changelog

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

1.46.0

Minor Changes

• #14724 a50f73a Thanks @​jamesopstad! - Add a settings export to the experimental cloudflare.config.ts config

  Account-level settings (accountId, complianceRegion) now live in a dedicated, named settings export authored via defineSettings, rather than on the Worker config. A cloudflare.config.ts can export at most one settings object; the Worker itself is the default export.

  // cloudflare.config.ts
  import { defineSettings, defineWorker } from "wrangler/experimental-config";
  import * as entrypoint from "./src/index.ts" with { type: "cf-worker" };
  export const settings = defineSettings({
  accountId: "<your-account-id>",
  });
  export default defineWorker({
  name: "my-worker",
  entrypoint,
  compatibilityDate: "2026-05-18",
  });

  This is only used behind the experimental new-config path (wrangler --experimental-new-config and the @cloudflare/vite-plugin experimental.newConfig option).

Patch Changes

• Updated dependencies [42af66d, a0a091b, f03b108, deae171, 0df3d43, d83a476, 4e92e32, d1d6945, 4815711, a0c8bb1, a50f73a, 2b390d7, c82d96b, 34430b3, f75ae5d]:
  • miniflare@4.20260721.0
  • wrangler@4.113.0

Commits

• 88f42e7 Version Packages (#14740)
• 0df3d43 [wrangler] Extract remote bindings into a package (#14720)
• a50f73a Support settings export in new config (#14724)
• 6687a91 docs: React Router v7 -> v8 in vite plugin README (#14757)
• ec2600e Enable @typescript-eslint/no-deprecated linting rule for `vite-plugin-cloud...
• See full diff in compare view

Updates @cloudflare/vitest-pool-workers from 0.18.6 to 0.18.7

Release notes

Sourced from @​cloudflare/vitest-pool-workers's releases.

@​cloudflare/vitest-pool-workers@​0.18.7

Patch Changes

• #14713 de34449 Thanks @​allocsys! - Fix a non-ASCII path failure during the Miniflare WebSocket handshake: the MF-Vitest-Worker-Data header embedded the raw process.cwd() value, which threw a Latin-1/ASCII header encoding error when the workspace path contained non-ASCII characters (e.g. CJK characters) on Windows. The value is now percent-encoded on write and decoded on read, matching the fix applied to the module fallback redirect response.

• #14713 de34449 Thanks @​allocsys! - Fix a runtime start-up failure ("No such module "cloudflare:test-internal"") when the project workspace path contains non-ASCII characters (e.g. CJK characters) on Windows. The module fallback service's redirect response set the target file path directly as an HTTP Location header value, but headers are restricted to the Latin-1/ASCII byte range, so any non-ASCII byte in the path caused header construction to throw. Such paths are now percent-encoded (and tagged with a sentinel prefix) before being used as a header value, and decoded again only for the values we encoded, so the round-trip is unambiguous and a workspace path containing a literal % is left untouched instead of being mis-decoded.

• #14739 5eac99e Thanks @​Ankcorn! - Support testing Streaming Tail Workers in Vitest Pool Workers.

• #14763 538e867 Thanks @​gianghungtien! - Treat webSocketMessage(), webSocketClose() and webSocketError() as optional Durable Object handlers

  The pool wraps each Durable Object class and installs a prototype method for every default handler before user code is loaded, so workerd always sees a handler and always dispatches. When the wrapped class didn't actually define one, the wrapper threw <ClassName> exported by <path> does not define a `webSocketClose()` method, even though deployed Workers silently ignore these events for classes that omit them. A hibernatable Durable Object defining only webSocketMessage() would log an uncaught TypeError on every close.

  These three handlers now no-op when absent, matching deployed behaviour. alarm() is unchanged and still reports a missing handler, since workerd rejects setAlarm() up front on a class without one.

• Updated dependencies [42af66d, a0a091b, f03b108, deae171, 0df3d43, d83a476, 4e92e32, d1d6945, 4815711, a0c8bb1, a50f73a, 2b390d7, c82d96b, 34430b3, f75ae5d]:

  • miniflare@4.20260721.0
  • wrangler@4.113.0

Changelog

Sourced from @​cloudflare/vitest-pool-workers's changelog.

0.18.7

Patch Changes

• #14713 de34449 Thanks @​allocsys! - Fix a non-ASCII path failure during the Miniflare WebSocket handshake: the MF-Vitest-Worker-Data header embedded the raw process.cwd() value, which threw a Latin-1/ASCII header encoding error when the workspace path contained non-ASCII characters (e.g. CJK characters) on Windows. The value is now percent-encoded on write and decoded on read, matching the fix applied to the module fallback redirect response.

• #14713 de34449 Thanks @​allocsys! - Fix a runtime start-up failure ("No such module "cloudflare:test-internal"") when the project workspace path contains non-ASCII characters (e.g. CJK characters) on Windows. The module fallback service's redirect response set the target file path directly as an HTTP Location header value, but headers are restricted to the Latin-1/ASCII byte range, so any non-ASCII byte in the path caused header construction to throw. Such paths are now percent-encoded (and tagged with a sentinel prefix) before being used as a header value, and decoded again only for the values we encoded, so the round-trip is unambiguous and a workspace path containing a literal % is left untouched instead of being mis-decoded.

• #14739 5eac99e Thanks @​Ankcorn! - Support testing Streaming Tail Workers in Vitest Pool Workers.

• #14763 538e867 Thanks @​gianghungtien! - Treat webSocketMessage(), webSocketClose() and webSocketError() as optional Durable Object handlers

  The pool wraps each Durable Object class and installs a prototype method for every default handler before user code is loaded, so workerd always sees a handler and always dispatches. When the wrapped class didn't actually define one, the wrapper threw <ClassName> exported by <path> does not define a `webSocketClose()` method, even though deployed Workers silently ignore these events for classes that omit them. A hibernatable Durable Object defining only webSocketMessage() would log an uncaught TypeError on every close.

  These three handlers now no-op when absent, matching deployed behaviour. alarm() is unchanged and still reports a missing handler, since workerd rejects setAlarm() up front on a class without one.

• Updated dependencies [42af66d, a0a091b, f03b108, deae171, 0df3d43, d83a476, 4e92e32, d1d6945, 4815711, a0c8bb1, a50f73a, 2b390d7, c82d96b, 34430b3, f75ae5d]:

  • miniflare@4.20260721.0
  • wrangler@4.113.0

Commits

• 88f42e7 Version Packages (#14740)
• 0df3d43 [wrangler] Extract remote bindings into a package (#14720)
• 538e867 [vitest-pool-workers] Treat webSocket* as optional Durable Object handlers ...
• de34449 [vitest-pool-workers] Fix module fallback failure on non-ASCII workspace path...
• 5eac99e [vitest-pool-workers] Support streaming tails to the main worker (#14739)
• See full diff in compare view

Updates @types/node from 22.20.1 to 26.1.1

Commits

• See full diff in compare view

Updates typescript from 6.0.3 to 7.0.2

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.

Updates wrangler from 4.112.0 to 4.113.0

Release notes

Sourced from wrangler's releases.

wrangler@4.113.0

Minor Changes

• #14471 f03b108 Thanks @​DiogoSantoss! - Apply Email Routing addresses during Worker trigger deployment

  Worker trigger deployment now reconciles the Worker's Email Routing rules with the top-level addresses config. This runs for wrangler deploy, wrangler triggers deploy, and clients of @cloudflare/deploy-helpers. After the Worker uploads, or when wrangler triggers deploy runs after a version promotion, the deploy helper asks the Email Routing API for a plan, renders the changes grouped by zone (+ added, ~ updated, - deleted, ! conflict), prompts once for destructive changes in interactive mode, and applies accepted changes through the per-zone rule endpoints. Purely additive plans apply without a prompt, while non-interactive destructive plans fail without modifying rules.

• #14679 deae171 Thanks @​dario-piotrowicz! - Add exclude_packages option to dependencies_instrumentation configuration

  The dependencies_instrumentation config object now accepts an optional exclude_packages field — an array of package name patterns (with glob-style * wildcards) to exclude from the dependency metadata collected during deploy and version uploads.

  // wrangler.json
  {
    "dependencies_instrumentation": {
      "exclude_packages": ["@internal/*", "secret-tool"]
    }
  }

• #14721 4e92e32 Thanks @​dmmulroy! - Support Artifacts sources when creating Queue event subscriptions

  wrangler queues subscription create now accepts the artifacts and artifacts.repo source types supported by the Cloudflare API.

• #13352 d1d6945 Thanks @​penalosa! - Expand automatic resource provisioning to Queue, Dispatch Namespace, and Flagship bindings

  Deployments can now omit the resource name or ID for these bindings. Wrangler will inherit the existing binding on subsequent deploys, create a deterministically named resource automatically, or offer existing resources during an interactive deploy with automatic creation disabled.

• #14688 a0c8bb1 Thanks @​NuroDev! - Print Local Explorer API details for headless agent-driven wrangler dev sessions

  When wrangler dev is started in a headless AI agent environment, Wrangler now prints the Local Explorer API URL and basic resource routes so agents can inspect local Workers and bindings without relying on the interactive UI.

• #14724 a50f73a Thanks @​jamesopstad! - Add a settings export to the experimental cloudflare.config.ts config

  Account-level settings (accountId, complianceRegion) now live in a dedicated, named settings export authored via defineSettings, rather than on the Worker config. A cloudflare.config.ts can export at most one settings object; the Worker itself is the default export.

  // cloudflare.config.ts
  import { defineSettings, defineWorker } from "wrangler/experimental-config";
  import * as entrypoint from "./src/index.ts" with { type: "cf-worker" };
  export const settings = defineSettings({
  accountId: "<your-account-id>",
  });
  export default defineWorker({
  name: "my-worker",
  entrypoint,
  compatibilityDate: "2026-05-18",
  });

... (truncated)

Commits

• 88f42e7 Version Packages (#14740)
• 9e61971 unskip agent memory remote bindings test (#14786)
• 0df3d43 [wrangler] Extract remote bindings into a package (#14720)
• 4815711 [miniflare] Report the Worker's error for HEAD requests (#14766)
• 
  ^{Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.}

  ---

  Summary by cubic

  Bump 15 dependencies across the repo to pick up bug fixes, small performance improvements, and Cloudflare tooling updates. Notable changes include typescript@7, @types/node@26, and updated React/Radix UI packages.

  • Dependencies

    • Runtime/UI: react/react-dom 19.2.8, radix-ui 1.6.3, @tanstack/react-query 5.101.4, @tanstack/react-start 1.168.32, @fontsource-variable/geist 5.3.0
    • Analytics: posthog-js 1.406.2, posthog-node 5.46.0
    • Cloudflare toolchain: wrangler 4.113.0, @cloudflare/vite-plugin 1.46.0, @cloudflare/vitest-pool-workers 0.18.7, @cloudflare/workers-types 5.20260722.1
    • Types/tooling: typescript 7.0.2, @types/node 26.x
    • SDKs: @llamaindex/llama-cloud 2.12.0

  • Migration

    • Ensure Node 22.14+ locally.
    • Run a full typecheck and tests; fix any new TypeScript 7 or Node 26 type errors.
    • No config changes are required for Cloudflare; optional new cloudflare.config.ts settings export is supported.

  ^{Written for commit ec4a315. Summary will update on new commits.}

  

[greptile-apps]

PR author is in the excluded authors list.