chore(deps-dev): bump wrangler from 4.75.0 to 4.110.0

[dependabot]

Bumps wrangler from 4.75.0 to 4.110.0.

Release notes

Sourced from wrangler's releases.

wrangler@4.110.0

Minor Changes

• #14591 0283a1f Thanks @​dario-piotrowicz! - Send npm package dependency metadata with worker uploads

  Wrangler now collects npm package dependency information from the project's package.json at deploy and version upload time, and includes it in the upload metadata sent to the Cloudflare API. This enables dependency analytics and future features like vulnerability alerting.

  The collected data includes the package name, the version constraint from package.json, and the exact installed version from node_modules. Both dependencies and devDependencies are included, while workspace packages, local packages, and unresolvable packages are excluded. The list is capped at 200 entries per upload.

  To opt out, set dependencies_instrumentation.enabled to false in your Wrangler configuration file:

  {
    "dependencies_instrumentation": {
      "enabled": false
    }
  }

• #14535 1b965c5 Thanks @​Naapperas! - Support dynamic retry delays for Workflow steps in local dev

  A step's retries.delay can now be a function that computes the delay per failed attempt, in addition to a static duration. The function receives { ctx, error } and returns a delay (a number of milliseconds or a duration string like "30 seconds"), and its result is fed into the configured backoff.

  await step.do(
    "call flaky API",
    {
      retries: {
        limit: 5,
        backoff: "constant",
        delay: ({ ctx }) => ctx.attempt * 1000,
      },
    },
    async () => {
      /* ... */
    }
  );

  The function is invoked once per failed attempt with a 5 second timeout. If it throws, times out, or returns an invalid value, the step fails without further retries.

Patch Changes

• #14589 7b28392 Thanks @​jamesopstad! - Fix runtime type caching when wrangler dev auto-regenerates types

  When dev.generate_types (or wrangler dev --types) regenerated an out-of-date worker-configuration.d.ts, the written file omitted the // Begin runtime types marker (and the /* eslint-disable */ header) that wrangler types writes. As a result, later runs could not detect the cached runtime types and always regenerated them. The auto-regenerated file now matches wrangler types output, restoring the cache.

• Updated dependencies [1b965c5]:

  • miniflare@4.20260708.1

... (truncated)

Commits

• eced610 Version Packages (#14628)
• 7b28392 Move runtime type generation to dedicated internal package (#14589)
• 0283a1f [wrangler] Add dependency metadata to worker uploads (#14591)
• 774c09e Version Packages (#14603)
• 2fedb1f Support workflow terminate rollback (#14465)
• c782e2a [wrangler] Restrict name-ownership guard to Pages-to-Workers delegation (#14616)
• 17d2fc1 [wrangler] Add turnstile widget CLI commands (#14511)
• 315c77c chore: use catalog for workerd dependency (#14607)
• 9f74a5f Workflows: Improve scheduled Workflows free-plan deploy error (#14604)
• 394b8ae Fix wrangler linting (failing because of deprecated detectAgenticEnvironment ...
• Additional commits viewable in compare view

[CircleCrop]

@copilot @codex

[CircleCrop]

@dependabot rebase

[chatgpt-codex-connector]

Summary

• Confirmed the dependency bump is already present: wrangler is set to ^4.78.0 in root dev dependencies. package.jsonL45-L51
• Confirmed the lockfile resolves wrangler to 4.78.0. pnpm-lock.yamlL47-L49 pnpm-lock.yamlL3046-L3048
• No code changes were needed, so I did not create a commit or open a new PR.

Testing

• ✅ pnpm install --frozen-lockfile
• ✅ pnpm typecheck

View task →

[CircleCrop]

@copilot review bump wrangler from 4.75.0 to 4.110.0

[Copilot]

@copilot review bump wrangler from 4.75.0 to 4.110.0

Reviewed commit e16497e: it only updates the wrangler devDependency and regenerates pnpm-lock.yaml. I validated with pnpm install --frozen-lockfile and pnpm --filter @magic-compare/internal-site lint (Node v22.23.1); both passed, so no additional code changes are needed.

[CircleCrop]

@dependabot update

[dependabot]

Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[CircleCrop]

@dependabot recreate