chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@babel/core (source)	7.26.9 -> 7.26.10
cookie	0.7.1 -> 0.7.2
lint-staged	15.4.3 -> 15.5.0
start-server-and-test	2.0.10 -> 2.0.11
wrangler (source)	3.114.0 -> 3.114.1

---

Release Notes

babel/babel (@​babel/core)

v7.26.10

Compare Source

👓 Spec Compliance

• babel-parser
  • #​17159 Disallow decorator in array pattern (@​JLHwung)

🐛 Bug Fix

• babel-parser, babel-template
  • #​17164 Fix: always initialize ExportDeclaration attributes (@​JLHwung)
• babel-core
  • #​17142 fix: "Map maximum size exceeded" in deepClone (@​liuxingbaoyu)
• babel-parser, babel-plugin-transform-typescript
  • #​17154 Update typescript parser tests (@​JLHwung)
• babel-traverse
  • #​17151 fix: Should not evaluate vars in child scope (@​liuxingbaoyu)
• babel-generator
  • #​17153 fix: Correctly generate abstract override (@​liuxingbaoyu)
• babel-parser
  • #​17107 Fix source type detection when parsing TypeScript (@​JLHwung)

💅 Polish

• babel-standalone
  • #​17158 Avoid warnings when re-bundling @​babel/standalone with webpack (@​liuxingbaoyu)

🏠 Internal

• babel-parser
  • #​17160 Left-value parsing cleanup (@​JLHwung)

jshttp/cookie (cookie)

v0.7.2

Compare Source

Fixed

• Fix object assignment of hasOwnProperty (#​177) bc38ffd

lint-staged/lint-staged (lint-staged)

v15.5.0

Compare Source

Minor Changes

• #​1526 630af5f Thanks @​iiroj! - Lint-staged no longer resets to the original state when preventing an empty git commit. This happens when your configured tasks reset all the staged changes, typically when trying to commit formatting changes which conflict with your linter setup like ESLint or Prettier.

Example with Prettier

By default Prettier prefers double quotes.

Previously

1. Stage file.js with only double quotes " changed to '
2. Run git commit -am "I don't like double quotes"
3. Lint-staged runs prettier --write file.js, converting all the ' back to "
4. Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state
5. Commit was not done, original state is restored and single quotes ' are staged

Now

1. Stage file.js with only double-quotes " changed to '
2. Run git commit -am "I don't like double quotes"
3. Lint-staged runs prettier --write file.js, converting all the ' back to "
4. Because there are now no changes, lint-staged fails and cancels the commit
5. Commit was not done, and there are no staged changes

bahmutov/start-server-and-test (start-server-and-test)

v2.0.11

Compare Source

cloudflare/workers-sdk (wrangler)

v3.114.1

Compare Source

Patch Changes

• #​8383 8d6d722 Thanks @​matthewdavidrodgers! - Make kv bulk put --local respect base64:true

  The bulk put api has an optional "base64" boolean property for each key.
  Before storing the key, the value should be decoded from base64.

  For real (remote) kv, this is handled by the rest api. For local kv, it
  seems the base64 field was ignored, meaning encoded base64 content was
  stored locally rather than the raw values.

  To fix, we need to decode each value before putting to the local
  miniflare namespace when base64 is true.

• #​8273 e3efd68 Thanks @​penalosa! - Support AI, Vectorize, and Images bindings when using @cloudflare/vite-plugin

• #​8427 a352798 Thanks @​vicb! - update unenv-preset dependency to fix bug with Performance global

  Fixes #​8407
  Fixes #​8409
  Fixes #​8411

• #​8390 53e6323 Thanks @​GregBrimble! - Parse and apply metafiles (_headers and _redirects) in wrangler dev for Workers Assets

• #​8392 4d9d9e6 Thanks @​jahands! - fix: retry zone and route lookup API calls

  In rare cases, looking up Zone or Route API calls may fail due to transient errors. This change improves the reliability of wrangler deploy when these errors occur.

  Also fixes a rare issue where concurrent API requests may fail without correctly throwing an error which may cause a deployment to incorrectly appear successful.

• Updated dependencies [8242e07, 53e6323]:

  • miniflare@3.20250310.0

---

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.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @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://f0d271af.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% ✓ 838878      ✗ 0     
     data_received...............................: 76 MB   634 kB/s
     data_sent...................................: 53 MB   444 kB/s
     http_req_blocked............................: avg=1.59µs   min=922ns    med=1.48µs   max=275.06µs p(90)=1.99µs   p(95)=2.15µs  
     http_req_connecting.........................: avg=1ns      min=0s       med=0s       max=133.52µs p(90)=0s       p(95)=0s      
     http_req_duration...........................: avg=204.44µs min=138.71µs med=193.08µs max=9.04ms   p(90)=220.76µs p(95)=230.4µs 
       { expected_response:true }................: avg=204.44µs min=138.71µs med=193.08µs max=9.04ms   p(90)=220.76µs p(95)=230.4µs 
     ✓ { server:node-http,mode:json-schema }.....: avg=219.88µs min=162.32µs med=207.78µs max=6.62ms   p(90)=232.56µs p(95)=241.61µs
     ✓ { server:node-http,mode:no-schema }.......: avg=210.62µs min=148.52µs med=196.41µs max=8.63ms   p(90)=221.83µs p(95)=233.18µs
     ✓ { server:uWebSockets,mode:json-schema }...: avg=198.94µs min=147.03µs med=188.94µs max=7.06ms   p(90)=211.58µs p(95)=218.7µs 
     ✓ { server:uWebSockets,mode:no-schema }.....: avg=190.23µs min=138.71µs med=179.86µs max=9.04ms   p(90)=203µs    p(95)=210.77µs
     http_req_failed.............................: 0.00%   ✓ 0           ✗ 419439
     http_req_receiving..........................: avg=23.68µs  min=12.02µs  med=22.85µs  max=3.25ms   p(90)=28.19µs  p(95)=30.68µs 
     http_req_sending............................: avg=9.2µs    min=5.33µs   med=9.19µs   max=428.09µs p(90)=12.18µs  p(95)=14.07µs 
     http_req_tls_handshaking....................: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting............................: avg=171.55µs min=111.99µs med=160.76µs max=8.97ms   p(90)=186.09µs p(95)=194.98µs
     http_reqs...................................: 419439  3495.286921/s
     iteration_duration..........................: avg=281.08µs min=200.71µs med=269.08µs max=9.21ms   p(90)=299.9µs  p(95)=311.52µs
     iterations..................................: 419439  3495.286921/s
     vus.........................................: 1       min=1         max=1   
     vus_max.....................................: 2       min=2         max=2