Bump wrangler from 4.98.0 to 4.99.0 in /website

[dependabot]

Bumps wrangler from 4.98.0 to 4.99.0.

Release notes

Sourced from wrangler's releases.

wrangler@4.99.0

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>@100%

... (truncated)

Commits

• 8a4bfe5 Version Packages (#14179)
• f8d7700 feat(wrangler): capture runtime logs and print debug timelines with `createTe...
• 4bb572f Bump the workerd-and-workers-types group with 2 updates (#14231)
• dcd116a feat(wrangler): improve createTestHarness() configuration setup (#14227)
• 75e652a Revert "Make Ctrl+C triggered during the skills-install prompt dismiss it per...
• e13b8c0 [C3] Bump @​angular/create from 21.2.13 to 22.0.0 in /packages/create-cloudfla...
• a61ac29 [wrangler] Add --version-tag support to versions deploy (#14211)
• 24497d0 Bump the workerd-and-workers-types group with 2 updates (#14217)
• 0706fbf feat(wrangler): createTestHarness API (#14169)
• 8923f97 Preserve all deployment-affecting CLI flags in the interactive deploy config ...
• Additional commits viewable in compare view