Skip to content

fix(deps): update workers-sdk derived dependencies - #637

Open
ant-release-bot wants to merge 1 commit into
mainfrom
renovate/workers-sdk
Open

ant-release-bot wants to merge 1 commit into
mainfrom
renovate/workers-sdk

Conversation

@ant-release-bot

Copy link
Copy Markdown
Collaborator

This PR contains the following updates:

Package Change Age Confidence
@cloudflare/autoconfig (source) 0.12.1 → 0.13.0 age confidence
@cloudflare/cli-shared-helpers (source) 0.3.8 → 0.3.9 age confidence
@cloudflare/codemods (source) 0.7.8 → 0.8.0 age confidence
@cloudflare/containers-shared (source) 0.26.1 → 0.26.2 age confidence
@cloudflare/deploy-helpers (source) 0.27.0 → 0.27.1 age confidence
@cloudflare/runtime-types (source) 0.1.28 → 0.1.29 age confidence
@cloudflare/workers-auth (source) 0.18.2 → 0.18.3 age confidence
@cloudflare/workers-utils (source) 0.54.0 → 0.54.1 age confidence
miniflare (source) 5.20261113.0-beta → 5.20261116.0-beta age confidence

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Release Notes

cloudflare/workers-sdk (@​cloudflare/autoconfig)

v0.13.0

Compare Source

Minor Changes
  • #​16803 b219078 Thanks @​petebacondarwin! - Run experimental cf projects with their installed Vite or Vite+ commands

    cf dev, cf build, and deployments that build your project can use Vite or Vite+ even when no framework command is detected. This removes the need for the internal cf-vite delegate and supports dependencies declared and hoisted at the root of a configured workspace. A workspace application using a custom-named Vite config should declare @cloudflare/vite-plugin in its own manifest, or add vite or vite-plus as a dependency or dev dependency to identify its tooling; this keeps shared root tools from selecting Vite for non-Vite siblings. Configs passed later via --config are evaluated by Vite when the command runs. Existing framework commands keep their priority. Consumers resolve bare executables using the detected nodeModulesPaths in order, adding .bin to each directory. Lookup stops at the validated workspace root; standalone applications use only their own node_modules/.bin.

    Project inspection can recognize an existing Cloudflare configuration before dependencies are installed. Running a command provides guidance when the required tools are missing or the plugin version does not support cf profiles (>=2.0.0-beta.v.13 <3). Vite evaluates the project configuration when the command runs, including dynamic configs and custom config files. Repair guidance uses the project’s detected package manager. Automatic setup asks users to convert CommonJS .cjs and .cts Vite configs to ESM imports and exports in .mjs or .mts before adding the ESM-only Cloudflare plugin. Native builds also work with the Windows shell. Pages migration safeguards, unsupported-framework setup checks, and Wrangler command selection retain their existing behavior.

Patch Changes
cloudflare/workers-sdk (@​cloudflare/cli-shared-helpers)

v0.3.9

Compare Source

Patch Changes
cloudflare/workers-sdk (@​cloudflare/codemods)

v0.8.0

Compare Source

Minor Changes
  • #​16246 349fc4e Thanks @​leostera! - Start local Workflows from Artifacts events

    Declare Artifacts events on exports.workflow({ name, events }) in cloudflare.config.ts to start the owning Workflow locally in cf, Vite, and Workers Vitest. Wrangler configurations continue to use triggers.events. Native config conversion derives those targets from the Workflow export, and cf migrate attaches existing event subscriptions to their matching Workflow exports.

    Local Artifacts namespaces publish the documented cf.artifacts.* messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions.

Patch Changes
  • #​16907 0bf81ac Thanks @​jamesopstad! - Generate the release candidate @cloudflare/config field names in wrangler-to-cf

    The codemod now writes:

    • first_party_worker as experimental.firstPartyWorker
    • Pipelines bindings as bindings.pipeline({ streamId })
    • K2 bindings as bindings.k2({ id })
    • the Analytics SQL binding as bindings.analyticsSql()

    A Pipelines binding that uses the deprecated pipeline field gets a STREAM_ID placeholder and a follow-up asking for the stream ID, because that field names a legacy pipeline, which @cloudflare/config doesn't support.

  • #​16921 6785363 Thanks @​jamesopstad! - Install the Vite plugin release candidate in wrangler-to-cf

    The Wrangler-to-cf migration now installs @cloudflare/vite-plugin@^2.0.0-rc.0 instead of the beta dist tag, which no longer receives new releases. It upgrades projects whose plugin is declared as a dist tag or resolves to a version older than the release candidate, since earlier betas don't support the generated configuration. The range also covers the stable v2 releases, so the migration no longer rewrites package.json to a dist tag after installing.

  • #​16946 e97c9f8 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

cloudflare/workers-sdk (@​cloudflare/containers-shared)

v0.26.2

Compare Source

Patch Changes
cloudflare/workers-sdk (@​cloudflare/deploy-helpers)

v0.27.1

Compare Source

Patch Changes
cloudflare/workers-sdk (@​cloudflare/runtime-types)

v0.1.29

Compare Source

Patch Changes
cloudflare/workers-sdk (@​cloudflare/workers-auth)

v0.18.3

Compare Source

Patch Changes
  • #​16946 e97c9f8 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #​16874 4335eac Thanks @​petebacondarwin! - Avoid redundant OAuth refreshes after a sibling process updates credentials

    Check access-token expiry and select the refresh token from the same fresh credential snapshot. When a sibling has already saved a valid access token, reuse it without another exchange or write. This prevents an unnecessary rotation that can let an older response overwrite a newer refresh token.

  • Updated dependencies [e97c9f8, 349fc4e]:

cloudflare/workers-sdk (@​cloudflare/workers-utils)

v0.54.1

Compare Source

Patch Changes
  • #​16946 e97c9f8 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #​16246 349fc4e Thanks @​leostera! - Start local Workflows from Artifacts events

    Declare Artifacts events on exports.workflow({ name, events }) in cloudflare.config.ts to start the owning Workflow locally in cf, Vite, and Workers Vitest. Wrangler configurations continue to use triggers.events. Native config conversion derives those targets from the Workflow export, and cf migrate attaches existing event subscriptions to their matching Workflow exports.

    Local Artifacts namespaces publish the documented cf.artifacts.* messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions.

cloudflare/workers-sdk (miniflare)

v5.20261116.0-beta

Compare Source

Minor Changes
  • #​16246 349fc4e Thanks @​leostera! - Start local Workflows from Artifacts events

    Declare Artifacts events on exports.workflow({ name, events }) in cloudflare.config.ts to start the owning Workflow locally in cf, Vite, and Workers Vitest. Wrangler configurations continue to use triggers.events. Native config conversion derives those targets from the Workflow export, and cf migrate attaches existing event subscriptions to their matching Workflow exports.

    Local Artifacts namespaces publish the documented cf.artifacts.* messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions.

  • #​16907 0bf81ac Thanks @​jamesopstad! - Rename the Pipelines, K2 and Analytics SQL env binding fields to match @cloudflare/config

    Config-style env bindings now use these shapes:

    • { type: "pipeline", streamId } instead of { type: "pipeline", name }
    • { type: "k2", id } instead of { type: "k2", stream }
    • { type: "analytics-sql" } instead of { type: "analytics" }
Patch Changes
  • #​16946 e97c9f8 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #​16946 e97c9f8 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261113.1 ^5.20261116.1
    workerd 1.20261113.1 1.20261116.1

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate CLI.

@ant-release-bot
ant-release-bot requested a review from a team as a code owner November 16, 2026 12:27
@ant-release-bot ant-release-bot added the dependencies Pull requests that update a dependency file label Nov 16, 2026
@pkg-pr-new

pkg-pr-new Bot commented Nov 16, 2026

Copy link
Copy Markdown
npm i https://pkg.pr.new/cf@637

commit: 7bc3b5b

@clanky-the-clanker clanky-the-clanker Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Minor issues — One WARNING with production impact: @cloudflare/deploy-helpers 0.27.1 moves to Build Output v1 and @cloudflare/config 1.0.0-rc.0, but cf still pins @cloudflare/build-output-utils 0.9.14 and @cloudflare/config 0.32.1. That leaves two incompatible format versions in the shipped CLI.

Findings: 1 warning (1 is an inline comment on the diff)

The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.

🔧 Fix with your agent

Paste the following into your coding agent to investigate and fix these issues.

Fix the following code review issues found in pull request #637.

Before making changes, review each issue and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g., the fix would require disproportionate changes
  for minimal ROI, or the finding is factually incorrect), explain why
- If you need to clarify something before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

## WARNING (1)

### [Code Quality] deploy-helpers 0.27.1 targets Build Output v1 and @cloudflare/config 1.0.0-rc.0, but cf still reads v0 output with build-output-utils 0.9.14 and config 0.32.1 and passes it to deploy-helpers. Preview deploys and other deploy paths may reject the config or read the account settings from the wrong place.
- **File:** packages/cli/package.json:87

📋 Code Quality: ⚠️ 1 warning

Build Output format version skew between deploy-helpers and the build-output-utils/config packages cf pins directly

Recommendation: 📝 Minor Comments

  • [WARNING] deploy-helpers 0.27.1 targets Build Output v1 and @​cloudflare/config 1.0.0-rc.0, but cf still reads v0 output with build-output-utils 0.9.14 and config 0.32.1 and passes it to deploy-helpers. Preview deploys and other deploy paths may reject the config or read the account settings from the wrong place. (packages/cli/package.json:87)
View full review

The upgrade to @cloudflare/deploy-helpers 0.27.1 brings in @cloudflare/config@1.0.0-rc.0 (see pnpm-lock.yaml:4330-4333). In its changelog, 0.27.1 also says it writes Build Output v1 to .cloudflare/output/v1/, nests account settings under settings and reads preview account settings from that new location. cf itself still pins @cloudflare/build-output-utils 0.9.14 and @cloudflare/config 0.32.1 (packages/cli/package.json:72-73). Those versions read the v0 layout, which the tests use (.cloudflare/output/v0/...). cf reads the root config with the old reader and passes it straight to deploy-helpers. For example, src/commands/previews/deploy.ts:111-123 calls readBuildOutput, then assertPreviewBuildOutputRootConfig(output.rootConfig), using output.rootConfig.accountId at the top level.


✅ All other checks passed

🚀 Release: ✅ LGTM

Overall risk: Low. The dependency refresh comes with a "cf": patch changeset, and its versions match the package manifests.


🔒 Security: ✅ LGTM

No security concerns in these dependency bumps.


📖 AGENTS.md: ✅ LGTM

No AGENTS.md changes needed.


⚡ Performance: ✅ LGTM

No performance concerns.


📝 Documentation: ✅ LGTM

The changeset accurately lists the version changes.


Reviewed commit: 7bc3b5ba

Comment thread packages/cli/package.json
"@cloudflare/cli-shared-helpers": "0.3.9",
"@cloudflare/codemods": "0.8.0",
"@cloudflare/containers-shared": "0.26.2",
"@cloudflare/deploy-helpers": "0.27.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ WARNING · Code Quality

deploy-helpers 0.27.1 targets Build Output v1 and @​cloudflare/config 1.0.0-rc.0, but cf still reads v0 output with build-output-utils 0.9.14 and config 0.32.1 and passes it to deploy-helpers. Preview deploys and other deploy paths may reject the config or read the account settings from the wrong place.

This bump brings in @cloudflare/config@1.0.0-rc.0 through deploy-helpers (pnpm-lock.yaml:4330-4333). Its changelog says it now writes and reads Build Output v1, with account settings nested under settings. cf still pins @cloudflare/build-output-utils 0.9.14 and @cloudflare/config 0.32.1 (lines 72-73). In src/commands/previews/deploy.ts:111-123, cf reads rootConfig with that old reader (top-level accountId) and hands it to assertPreviewBuildOutputRootConfig and the preview deploy from 0.27.1. Because deploy-helpers is bundled into the published CLI, preview deploys (and possibly other deploy paths) could fail or misread account settings. Consider upgrading @cloudflare/build-output-utils and @cloudflare/config to 1.0.0-rc.0 in this same pull request, and updating the v0 test fixtures, rather than shipping the two format versions side by side. Renovate's note says some dependencies could not be looked up, which may be why they were left out.

@github-actions

Copy link
Copy Markdown
Contributor

cf --help startup

mean stddev min max
PR 297.0 ms 5.4 ms 286.9 ms 303.7 ms
base 293.0 ms 4.1 ms 288.0 ms 302.5 ms

Δ (PR vs base): ↑ +4.1 ms (+1.4%)

Measured with hyperfine on ubuntu-latest (3 warmup runs, 20 timed runs). CI numbers carry ±a few ms of runner jitter; treat small deltas as noise.

Comment thread packages/cli/package.json Resolved
@ask-bonk

ask-bonk Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

Review: 2 findings.

Posted 2 inline findings on PR #637.

github run

@edmundhung
edmundhung removed the request for review from petebacondarwin November 16, 2026 12:36
@edmundhung

Copy link
Copy Markdown
Member

Looks like most of these bumps are already incorporated in #540. I will ask renovate to check again once that is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants