chore(deps-dev): bump wrangler from 4.28.0 to 4.28.1 in the dev-deps group

[dependabot]

Bumps the dev-deps group with 1 update: wrangler.

Updates wrangler from 4.28.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)
• See full diff 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

[cloudflare-workers-and-pages]

Deploying docs with    Cloudflare Pages

Latest commit:	1b4e601
Status:	✅  Deploy successful!
Preview URL:	https://583899b0.docs-51g.pages.dev
Branch Preview URL:	https://dependabot-npm-and-yarn-dev-ptqs.docs-51g.pages.dev

View logs

[github-actions]

Dangerous URL check

No absolute URLs to prisma.io/docs found.
No local URLs found.

[github-actions]

Redirect check

This PR probably requires the following redirects to be added to static/_redirects:

• This PR does not change any pages in a way that would require a redirect.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 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? Join our Discord community 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 sequence diagram to generate a sequence diagram of the changes in 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.