fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	22.13.2 -> 22.13.4
wrangler (source)	3.108.1 -> 3.109.0

---

Release Notes

cloudflare/workers-sdk (wrangler)

v3.109.0

Compare Source

Minor Changes

• #​8120 3fb801f Thanks @​sdnts! - Add a new update subcommand for Queues to allow updating Queue settings

• #​8120 3fb801f Thanks @​sdnts! - Allow overriding message retention duration when creating Queues

• #​8026 542c6ea Thanks @​penalosa! - Add --outfile to wrangler deploy for generating a worker bundle.

  This is an advanced feature that most users won't need to use. When set, Wrangler will output your built Worker bundle in a Cloudflare specific format that captures all information needed to deploy a Worker using the Worker Upload API

• #​8026 542c6ea Thanks @​penalosa! - Add a wrangler check startup command to generate a CPU profile of your Worker's startup phase.

  This can be imported into Chrome DevTools or opened directly in VSCode to view a flamegraph of your Worker's startup phase. Additionally, when a Worker deployment fails with a startup time error Wrangler will automatically generate a CPU profile for easy investigation.

  Advanced usage:

  • --args: to customise the way wrangler check startup builds your Worker for analysis, provide the exact arguments you use when deploying your Worker with wrangler deploy. For instance, if you deploy your Worker with wrangler deploy --no-bundle, you should use wrangler check startup --args="--no-bundle" to profile the startup phase.
  • --worker-bundle: if you don't use Wrangler to deploy your Worker, you can use this argument to provide a Worker bundle to analyse. This should be a file path to a serialised multipart upload, with the exact same format as the API expects: https://developers.cloudflare.com/api/resources/workers/subresources/scripts/methods/update/

Patch Changes

• #​8112 fff677e Thanks @​penalosa! - When reporting errors to Sentry, Wrangler will now include the console output as additional metadata

• #​8120 3fb801f Thanks @​sdnts! - Check bounds when overriding delivery delay when creating Queues

• #​7950 4db1fb5 Thanks @​cmackenzie1! - Add local binding support for Worker Pipelines

• #​8119 1bc60d7 Thanks @​penalosa! - Output correct config format from wrangler d1 create. Previously, this command would always output TOML, regardless of the config file format

• #​8130 1aa2a91 Thanks @​emily-shen! - Include default values for wrangler types --path and --x-include-runtime in telemetry

  User provided strings are still left redacted as always.

• #​8061 35710e5 Thanks @​emily-shen! - fix: respect WRANGLER_LOG in wrangler dev

  Previously, --log-level=debug was the only way to see debug logs in wrangler dev, which was unlike all other commands.

• Updated dependencies [4db1fb5]:

  • miniflare@3.20250204.1

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 was generated by Mend Renovate. View the repository job log.

[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.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @coderabbitai modularize this function.
• 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 generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

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. (Beta)
• @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.

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://647dbceb.fets.pages.dev

[github-actions]

✅ Benchmark Results

     ✓ no_errors{server:node-http,mode:no-schema}
     ✓ expected_result{server:node-http,mode:no-schema}
     ✓ no_errors{server:node-http,mode:json-schema}
     ✓ expected_result{server:node-http,mode:json-schema}
     ✓ no_errors{server:uWebSockets,mode:no-schema}
     ✓ expected_result{server:uWebSockets,mode:no-schema}
     ✓ no_errors{server:uWebSockets,mode:json-schema}
     ✓ expected_result{server:uWebSockets,mode:json-schema}

     checks......................................: 100.00% ✓ 844996      ✗ 0     
     data_received...............................: 77 MB   639 kB/s
     data_sent...................................: 54 MB   447 kB/s
     http_req_blocked............................: avg=1.63µs   min=911ns    med=1.55µs   max=3.09ms  p(90)=2.04µs   p(95)=2.23µs  
     http_req_connecting.........................: avg=7ns      min=0s       med=0s       max=2.82ms  p(90)=0s       p(95)=0s      
     http_req_duration...........................: avg=201.87µs min=136.68µs med=190.3µs  max=8.2ms   p(90)=217.24µs p(95)=226.91µs
       { expected_response:true }................: avg=201.87µs min=136.68µs med=190.3µs  max=8.2ms   p(90)=217.24µs p(95)=226.91µs
     ✓ { server:node-http,mode:json-schema }.....: avg=215.71µs min=159.83µs med=203.43µs max=8.2ms   p(90)=228.07µs p(95)=236.99µs
     ✓ { server:node-http,mode:no-schema }.......: avg=208.43µs min=152.62µs med=193.66µs max=7.33ms  p(90)=218.53µs p(95)=230.02µs
     ✓ { server:uWebSockets,mode:json-schema }...: avg=196.09µs min=143.99µs med=186.19µs max=7.33ms  p(90)=209.09µs p(95)=216.46µs
     ✓ { server:uWebSockets,mode:no-schema }.....: avg=188.91µs min=136.68µs med=178.37µs max=7.55ms  p(90)=201.58µs p(95)=209.67µs
     http_req_failed.............................: 0.00%   ✓ 0           ✗ 422498
     http_req_receiving..........................: avg=24.08µs  min=12.9µs   med=23.18µs  max=3.09ms  p(90)=28.71µs  p(95)=31.3µs  
     http_req_sending............................: avg=9.34µs   min=5.41µs   med=9.31µs   max=430.4µs p(90)=12.12µs  p(95)=14.04µs 
     http_req_tls_handshaking....................: avg=0s       min=0s       med=0s       max=0s      p(90)=0s       p(95)=0s      
     http_req_waiting............................: avg=168.44µs min=109.01µs med=157.51µs max=8.1ms   p(90)=182.19µs p(95)=191.16µs
     http_reqs...................................: 422498  3520.745427/s
     iteration_duration..........................: avg=279.03µs min=196.92µs med=266.73µs max=8.37ms  p(90)=296.85µs p(95)=308.81µs
     iterations..................................: 422498  3520.745427/s
     vus.........................................: 1       min=1         max=1   
     vus_max.....................................: 2       min=2         max=2