chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Update	Change	Pending	Age	Confidence
awscli	minor	2.34.63 → 2.35.1	2.35.6 (+4)
npm:@openai/codex (source)	minor	0.137.0 → 0.139.0	0.140.0
vercel (source)	minor	54.9.1 → 54.10.3	54.14.0 (+6)
wrangler (source)	minor	4.98.0 → 4.99.0	4.101.0 (+1)

---

Release Notes

aws/aws-cli (awscli)

v2.35.1

Compare Source

v2.35.0

Compare Source

v2.34.64

Compare Source

vercel/vercel (vercel)

v54.10.3

Compare Source

Patch Changes

• 4f82914: Bump the embedded sandbox CLI to 3.1.2 (@vercel/sandbox 2.1.1) to fix vc sandbox commands crashing with a segmentation fault.
  • @​vercel/node@​5.8.14

v54.10.2

Compare Source

Patch Changes

• 0f7844c: Fix the native CLI binary crashing on auth commands (login, whoami, logout, and any
  command that reads config) with ERR_MODULE_NOT_FOUND: '@​vercel/cli-auth'. The package is now
  staged into the binary. The binary release is also hardened with a real command smoke test and a
  build-time check that every statically-imported dependency is bundled, so a binary missing a
  required package can no longer be released.
• Updated dependencies [78e5d4f]
  • @​vercel/static-build@​2.10.0
  • @​vercel/hydrogen@​1.4.0
  • @​vercel/redwood@​2.5.0
  • @​vercel/remix-builder@​5.9.0
  • @​vercel/next@​4.18.0

v54.10.1

Compare Source

Patch Changes

• Updated dependencies [4e849dd]
  • @​vercel/build-utils@​13.28.0
  • @​vercel/next@​4.17.6
  • @​vercel/backends@​0.8.9
  • @​vercel/elysia@​0.1.90
  • @​vercel/express@​0.1.100
  • @​vercel/fastify@​0.1.93
  • @​vercel/go@​3.8.0
  • @​vercel/h3@​0.1.99
  • @​vercel/hono@​0.2.93
  • @​vercel/hydrogen@​1.3.8
  • @​vercel/koa@​0.1.73
  • @​vercel/nestjs@​0.2.94
  • @​vercel/node@​5.8.14
  • @​vercel/python@​6.44.0
  • @​vercel/redwood@​2.4.15
  • @​vercel/remix-builder@​5.8.6
  • @​vercel/ruby@​2.4.0
  • @​vercel/rust@​1.3.0
  • @​vercel/static-build@​2.9.39

v54.10.0

Compare Source

Minor Changes

• 0774460: Bump @​vercel/prepare-flags-definitions

Patch Changes

• f6a6e55: Only offer the Claude Code plugin in projects that have actually been used with Claude Code. Previously the prompt could appear in any directory as long as a ~/.claude directory existed on disk. The CLI now checks whether the current project (walking up from the working directory) appears in Claude Code's per-project history before offering the plugin.

• a4f7dc9: CLI help and command-schema cleanups from the docs audit:

  • blob: remove orphan addStoreSubcommand, removeStoreSubcommand, and getStoreSubcommand exports that duplicated the wired create-store / delete-store / get-store specs. Handlers and telemetry now import the actual wired subcommand definitions.
  • dns list: the <domain> argument is now declared required: false to match the runtime, which already supports listing every domain's records when no argument is given.
  • routes delete: declare the <name-or-id> argument as multiple: true so the help synopsis and schema match the variadic behavior already supported by the handler and shown in the existing examples.
  • init: fix the "Initialize example project into specified directory" help example, which was missing the init literal (vercel <example> <dir> → vercel init <example> <dir>).
  • promote status and rollback status: declare --timeout on the status subcommand options so --help matches the examples (promote status --timeout 30s, rollback status --timeout 30s). The flag is also kept on the parent command, where parsing actually happens.

• 33efa25: Added non-managed Connex connector creation with --data and optional --connector-type.

• 3a2d61e: Add vercel domains search <query> for client-side Domain Discovery with fast bulk availability and registrar pricing, renewal pricing, --available and exact TLD filters, ordering, candidate windows of up to 200 domains, and JSON output.

• c5eeb30: Gate the client-side 900-second maxDuration upper bound behind the VERCEL_CLI_SKIP_MAX_DURATION_LIMIT environment variable. The limit is now owned by a single helper in @vercel/build-utils instead of being hardcoded in multiple validators. When the variable is set to 1, the client-side maximum is skipped and validation defers to the server. Default behavior is unchanged — the maximum, the lower bound, and the integer check are all still enforced when the variable is unset.

• 9f9eed3: Nest Build Output API files for experimentalServicesV2 under .vercel/output/services/<name>.

• fb30b76: Strip ANSI escape sequences from connector UID and name cells in connect list table output.

• Updated dependencies [c5eeb30]

• Updated dependencies [09c39af]

  • @​vercel/build-utils@​13.27.2
  • @​vercel/static-build@​2.9.38
  • @​vercel/backends@​0.8.8
  • @​vercel/elysia@​0.1.89
  • @​vercel/express@​0.1.99
  • @​vercel/fastify@​0.1.92
  • @​vercel/go@​3.8.0
  • @​vercel/h3@​0.1.98
  • @​vercel/hono@​0.2.92
  • @​vercel/hydrogen@​1.3.8
  • @​vercel/koa@​0.1.72
  • @​vercel/nestjs@​0.2.93
  • @​vercel/next@​4.17.5
  • @​vercel/node@​5.8.13
  • @​vercel/python@​6.44.0
  • @​vercel/redwood@​2.4.15
  • @​vercel/remix-builder@​5.8.6
  • @​vercel/ruby@​2.4.0
  • @​vercel/rust@​1.3.0

cloudflare/workers-sdk (wrangler)

v4.99.0

Compare Source

Minor Changes

• #​14169 0706fbf Thanks @​edmundhung! - Introduce createTestHarness() for integration testing Workers

  It runs Workers in a local preview environment using production build output and works with both Wrangler projects and Workers built by the Cloudflare Vite plugin.

  Use it from any Node.js test runner to send requests to individual Workers, trigger scheduled events, reset the server between tests, and mock outbound requests with libraries that intercept globalThis.fetch(), such as MSW.

  You can also capture structured logs from your Workers with getLogs(), or dump out a diagnostic timeline with debug() when tests fail:

  import { createTestHarness } from "wrangler";
  
  const server = createTestHarness({
    workers: [
      { configPath: "./dist/web_worker/wrangler.json" },
      { configPath: "./dist/api_worker/wrangler.json" },
    ],
  });
  
  await server.listen();
  await server.fetch("http://example.com");
  
  const apiWorker = server.getWorker("api-worker");
  await apiWorker.fetch("http://example.com/users/123");
  await apiWorker.scheduled({ cron: "0 0 * * *" });
  
  server.getLogs();
  
  if (testFailed) {
    server.debug();
  }
  
  await server.reset();
  await server.close();

• #​14174 8cf8c61 Thanks @​oliy! - Surface pipeline status and failure reasons in wrangler pipelines list and wrangler pipelines get

  wrangler pipelines list now includes a Status column, and when any pipelines are in a failed state it prints a summary of each failing pipeline along with the reason reported by the API.

  wrangler pipelines get now shows the pipeline Status in the general details and, for failed pipelines, highlights the failure with the reason returned by the server so it is clear why a pipeline is not running.

• #​14211 a61ac29 Thanks @​james-elicx! - Add --version-tag support to wrangler versions deploy to deploy a version by its tag

  You can now roll out or roll back a version by the tag it was uploaded with (e.g. a commit SHA passed to --tag at upload time) instead of first looking up its Version ID:

  wrangler versions deploy --version-tag <sha>@&#8203;100%

  The tag is resolved to a Version ID against the worker's deployable versions, and the <version-tag>@&#8203;<percentage> shorthand works just like the existing <version-id>@&#8203;<percentage> notation, including splitting traffic across multiple --version-tag values. If a tag matches no deployable version, or matches more than one, the command errors and asks you to deploy by Version ID directly. Note that tags can only be resolved against recent (deployable) versions — older versions that have aged out of that window must still be deployed by Version ID.

Patch Changes

• #​14163 23aecac Thanks @​emily-shen! - Print deploy warnings even in non-interactive contexts when strict mode is off

  Currently, wrangler deploy checks whether the incoming deploy configuration has destructive conflicts with the current configuration. Previously, we only performed this check in interactive contexts, or if the --strict flag was passed in. Now this warning is always printed, and it remains non-blocking in non-interactive contexts.

• #​14173 b932e47 Thanks @​gpanders! - Handle API validation errors from wrangler containers ssh

  Wrangler now lets the Containers API validate SSH instance IDs and preserves raw API error bodies such as INVALID_INSTANCE_ID when reporting validation failures.

• #​14192 d076bcc Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260603.1	1.20260605.1

• #​14217 24497d0 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260605.1	1.20260608.1

• #​14231 4bb572f Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260608.1	1.20260609.1

• #​14195 165adb2 Thanks @​dario-piotrowicz! - Show actionable error message when authentication fails during remote dev

  When wrangler dev with remote bindings encountered an authentication error (expired token, revoked OAuth, or invalid API token), the user saw a generic "A request to the Cloudflare API failed" message with no indication that authentication was the problem.

  Now, authentication failures during remote dev display a clear error message with actionable steps.

• #​14034 776098c Thanks @​matingathani! - Fix wrangler types --check reporting types as out of date in multi-worker setups

  Previously, running wrangler types --check -c primary/wrangler.jsonc in a multi-worker project would incorrectly report types as out of date, even when they were current. This happened because the secondary worker config paths (passed via additional -c flags during generation) were not stored in the generated types file header, so --check had no way to resolve the secondary workers' service bindings when verifying the hash.

  The fix stores secondary config paths in the generated file's header comment so that --check can recover them automatically. Users no longer need to re-pass every -c flag when running --check — only the primary config is required.

• #​14053 7993711 Thanks @​fallintoplace! - Prevent delete-only wrangler secret bulk input from creating a new Worker

  Previously, wrangler secret bulk could create a draft Worker when the input only deleted secrets and the target Worker name did not exist. Delete-only bulk secret operations now leave Worker-not-found as an error instead of creating a new Worker.

• #​14055 8923f97 Thanks @​dario-piotrowicz! - Preserve all deployment-affecting CLI flags in the interactive deploy config flow

  When running wrangler deploy without a config file and going through the interactive setup flow, CLI flags beyond --compatibility-flags (such as --routes/--route, --domains/--domain, --triggers, --var, --define, --alias, --jsx-factory, --jsx-fragment, --tsconfig, --minify, --upload-source-maps, --no-bundle, --logpush, --keep-vars, --legacy-env, and --dispatch-namespace) were silently dropped. These flags are now persisted to the generated wrangler.jsonc config file (where a config field equivalent exists) and included in the suggested CLI command when the user declines config file generation.

• #​14196 b205fb7 Thanks @​odiak! - Validate JSON stdin values for wrangler secret bulk

  JSON input piped through stdin now validates that secret values are strings or null before sending them to the API, matching the existing behavior for file input.

• Updated dependencies [d076bcc, 24497d0, 4bb572f, 48c4ff0]:

  • miniflare@​4.20260609.0

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • At any time (no schedule defined)
• 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.