build(deps-dev): bump wrangler from 4.27.0 to 4.28.1 in the patch-versions group

[dependabot]

Bumps the patch-versions group with 1 update: wrangler.

Updates wrangler from 4.27.0 to 4.28.1

Release notes

Sourced from wrangler's releases.

wrangler@4.28.1

Patch Changes

• #10130 773cca3 Thanks @​dario-piotrowicz! - update maybeStartOrUpdateRemoteProxySession config argument (to allow callers to specify an environment)

  Before this change maybeStartOrUpdateRemoteProxySession could be called with either the path to a wrangler config file or the configuration of a worker. The former override however did not allow the caller to specify an environment, so the maybeStartOrUpdateRemoteProxySession API has been updated so that in the wrangler config case an object (with the path and a potential environment) needs to be passed instead.

  For example, before callers could invoke the function in the following way

  await maybeStartOrUpdateRemoteProxySession(configPath);

  note that there is no way to tell the function what environment to use when parsing the wrangle configuration.

  Now callers will instead call the function in the following way:

  await maybeStartOrUpdateRemoteProxySession({
  	path: configPath,
  	environment: targetEnvironment,
  });

  note that now a target environment can be specified.

• #10130 773cca3 Thanks @​dario-piotrowicz! - fix getPlatformProxy not taking into account the potentially specified environment for remote bindings

• #10122 2e8eb24 Thanks @​dario-piotrowicz! - fix startWorker not respecting auth options for remote bindings

  fix startWorker currently not taking into account the auth field that can be provided as part of the dev options when used in conjunction with remote bindings

  example:

  Given the following

  import { unstable_startWorker } from "wrangler";
  const worker = await unstable_startWorker({
  entrypoint: "./worker.js",
  bindings: {
  AI: {
  type: "ai",
  experimental_remote: true,
  },
  },
  dev: {

... (truncated)

Changelog

Sourced from wrangler's changelog.

4.28.1

Patch Changes

• #10130 773cca3 Thanks @​dario-piotrowicz! - update maybeStartOrUpdateRemoteProxySession config argument (to allow callers to specify an environment)

  Before this change maybeStartOrUpdateRemoteProxySession could be called with either the path to a wrangler config file or the configuration of a worker. The former override however did not allow the caller to specify an environment, so the maybeStartOrUpdateRemoteProxySession API has been updated so that in the wrangler config case an object (with the path and a potential environment) needs to be passed instead.

  For example, before callers could invoke the function in the following way

  await maybeStartOrUpdateRemoteProxySession(configPath);

  note that there is no way to tell the function what environment to use when parsing the wrangle configuration.

  Now callers will instead call the function in the following way:

  await maybeStartOrUpdateRemoteProxySession({
  	path: configPath,
  	environment: targetEnvironment,
  });

  note that now a target environment can be specified.

• #10130 773cca3 Thanks @​dario-piotrowicz! - fix getPlatformProxy not taking into account the potentially specified environment for remote bindings

• #10122 2e8eb24 Thanks @​dario-piotrowicz! - fix startWorker not respecting auth options for remote bindings

  fix startWorker currently not taking into account the auth field that can be provided as part of the dev options when used in conjunction with remote bindings

  example:

  Given the following

  import { unstable_startWorker } from "wrangler";
  const worker = await unstable_startWorker({
  entrypoint: "./worker.js",
  bindings: {
  AI: {
  type: "ai",
  experimental_remote: true,
  },
  },

... (truncated)

Commits

• d16de46 Version Packages (#10223)
• 93c4c26 fix: strip ANSI escape codes from wrangler log files (#10209)
• 2e8eb24 fix startWorker not respecting auth options for remote bindings (#10122)
• 773cca3 fix specified environments being ignored for remote bindings in some cases (#...
• 48853a6 validate container configuration in wrangler (#9774)
• 5bd0a19 stop vitest pool workers breaking when containers are present (#10162)
• 390b7fb Version Packages (#10156)
• ab59066 Move macOS version validation from @​cloudflare/cli to miniflare (#10211)
• dae1377 WC-3776 Require confirm for delete when Pages project binds to worker (#10186)
• 43b6f7b chore: rename old mixed-mode references to remote-bindings (#10134)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Summary by CodeRabbit

• Chores
  • Upgraded Wrangler dev dependency to ^4.28.1 to improve development tooling stability and compatibility.
  • No changes to runtime behavior, build outputs, or public API.
  • Scripts and package manager settings remain unchanged; CI/build workflows unaffected.
  • No user-facing impact or required actions.

[coderabbitai]

Walkthrough

Updated devDependency "wrangler" version in package.json from ^4.27.0 to ^4.28.1. No other fields or exports changed.

Changes

Cohort / File(s)	Summary of Changes
Dev Tooling Versions package.json	Bumped devDependency wrangler from ^4.27.0 to ^4.28.1; no other modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• build(deps-dev): bump wrangler from 4.24.3 to 4.25.0 in the patch-versions group #284: Also bumps the wrangler devDependency in package.json (to a different version).
• build(deps-dev): bump wrangler from 4.25.0 to 4.26.0 in the patch-versions group #290: Updates the same wrangler devDependency entry to another target version.
• build(deps-dev): bump wrangler from 4.26.0 to 4.27.0 in the patch-versions group #291: Modifies package.json to bump wrangler, targeting a different version.

Suggested reviewers

• akaladarshi
• LesnyRumcajs
• sudo-shashank

Poem

I nudge a number, hop and grin,
Wrangler’s stitched a fresher skin.
No routes to change, no code to mend—
Just versions stepping end-to-end.
Thump-thump! says my reviewer drum,
Quick glance, quick merge—job well done. 🐇✨

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dependabot/npm_and_yarn/patch-versions-6e6bf79d3c

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 016e231 and 841c976.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• package.json (1 hunks)

[coderabbitai]

💡 Verification agent

🧩 Analysis chain

Wrangler patch bump looks good; verify env config and lockfile resolution

• Change is scoped to a devDependency and aligns with Node >= 18. Low risk for production code.
• Given upstream changes around environment handling and remote bindings/auth, please verify that the --env quick used in scripts maps to a defined environment in wrangler.toml and that the lockfile pins 4.28.1.

Run this to validate env presence and lockfile resolution:

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "1) Confirm wrangler env 'quick' exists"
fd -i -a 'wrangler*.toml' || true
if rg -n '\[env\.quick\]' -S $(fd -i 'wrangler*.toml' | tr '\n' ' ') ; then
  echo "Found [env.quick] in wrangler config."
else
  echo "WARNING: [env.quick] not found in wrangler config files (wrangler*.toml)."
fi

echo
echo "2) Locate scripts referencing wrangler env usage"
rg -n --pretty 'wrangler\s+dev.*--env\s+quick|wrangler\s+build' -A 1 package.json || true

echo
echo "3) Verify package.json dependency range"
jq -r '.devDependencies.wrangler' package.json

echo
echo "4) Verify yarn.lock resolution (Yarn Berry)"
if [ -f yarn.lock ]; then
  rg -n '^wrangler@' -nA 3 yarn.lock | sed -n '1,20p'
else
  echo "No yarn.lock found."
fi

Length of output: 1474

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "1) Confirm [env.quick] in wrangler.toml"
if grep -q '^\[env\.quick\]' wrangler.toml; then
  echo "Found [env.quick] in wrangler.toml"
else
  echo "WARNING: [env.quick] not found in wrangler.toml"
fi

echo
echo "2) Verify yarn.lock resolution for wrangler@4.28.1"
if [ -f yarn.lock ]; then
  grep -n '^wrangler@' yarn.lock | head -n 20
else
  echo "No yarn.lock found."
fi

Length of output: 443

---

Add missing Wrangler environment and update lockfile

• wrangler.toml: no [env.quick] section was found — please add or verify the quick environment in your Wrangler config.
• package.json (line 21): you’re running wrangler dev --env quick; ensure that maps to a real env in wrangler.toml.
• yarn.lock: we didn’t find any wrangler@… entries — run yarn install (or yarn dedupe) to pick up the bumped ^4.28.1 and verify it’s pinned in your lockfile.

🤖 Prompt for AI Agents

In package.json around line 10 (and referenced script at line ~21) the repo
references wrangler@^4.28.1 and uses `--env quick` but wrangler.toml has no
`[env.quick]` section and yarn.lock lacks a pinned wrangler entry; add a
`[env.quick]` section to wrangler.toml (or change the package.json script to use
an existing environment), then run `yarn install` (or `yarn dedupe`/`yarn
install --check-files`) to update yarn.lock so wrangler@^4.28.1 is
recorded/pinned, and verify the package.json script and wrangler.toml env names
match.

[LesnyRumcajs]

@sudo-shashank, tests seemed to be failing on this update. Could you please check what is going on?

[LesnyRumcajs]

Superseded by #295

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml