fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@cloudflare/workers-types	4.20250519.0 -> 4.20250520.0
@pulumi/aws (source)	6.80.0 -> 6.81.0
@types/node (source)	22.15.19 -> 22.15.20
svelte (source)	5.31.1 -> 5.32.1
webpack	5.99.8 -> 5.99.9
wrangler (source)	4.15.2 -> 4.16.0

---

Release Notes

cloudflare/workerd (@​cloudflare/workers-types)

v4.20250520.0

Compare Source

pulumi/pulumi-aws (@​pulumi/aws)

v6.81.0

Compare Source

sveltejs/svelte (svelte)

v5.32.1

Compare Source

Patch Changes

• Warn when an invalid <select multiple> value is given (#​14816)

v5.32.0

Compare Source

Minor Changes

• feat: warn on implicitly closed tags (#​15932)

• feat: attachments fromAction utility (#​15933)

Patch Changes

• fix: only re-run directly applied attachment if it changed (#​15962)

webpack/webpack (webpack)

v5.99.9

Compare Source

cloudflare/workers-sdk (wrangler)

v4.16.0

Compare Source

Minor Changes

• #​9288 3b8f7f1 Thanks @​petebacondarwin! - allow --name and --env args on wrangler deploy

  Previously it was not possible to provide a Worker name as a command line argument at the same time as setting the Wrangler environment.
  Now specifying --name is supported and will override any names set in the Wrangler config:

  wrangler.json

  {
  	"name": "config-worker"
  	"env": {
  		"staging": { "name": "config-worker-env" }
  	}
  }

  Command	Previous (Worker name)	Proposed (Worker name)	Comment
  wrangler deploy --name=args-worker	"args-worker"	"args-worker"	CLI arg used
  wrangler deploy --name=args-worker --env=staging	Error	"args-worker"	CLI arg used
  wrangler deploy --name=args-worker --env=prod	Error	"args-worker"	CLI arg used
  wrangler deploy	"config-worker"	"config-worker"	Top-level config used
  wrangler deploy --env=staging	"config-worker-env"	"config-worker-env"	Named env config used
  wrangler deploy --env=prod	"config-worker-prod"	"config-worker-prod"	CLI arg and top-level config combined

• #​9265 16de0d5 Thanks @​edmundhung! - docs: add documentation links to individual config properties in the JSON schema of the Wrangler config file

Patch Changes

• #​9234 2fe6219 Thanks @​emily-shen! - fix: add no-op props to ctx in getPlatformProxy to fix type mismatch

• #​9269 66d975e Thanks @​dario-piotrowicz! - Wire up mixed-mode remote bindings for multi-worker wrangler dev

  Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a multi-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

  Also include the ai binding since the bindings is already remote by default anyways.

• #​9151 5ab035d Thanks @​gabivlj! - wrangler containers can be configured with the kind of application rollout on apply

• #​9231 02d40ed Thanks @​dario-piotrowicz! - Wire up mixed-mode remote bindings for (single-worker) wrangler dev

  Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a single-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

  Also include the ai binding since the bindings is already remote by default anyways.

• #​9221 2ef31a9 Thanks @​vicb! - bump @cloudflare/unenv-preset

• #​9277 db5ea8f Thanks @​penalosa! - Support Mixed Mode for more binding types

• #​9266 f2a16f1 Thanks @​petebacondarwin! - fix: setting triggers.crons:[] in Wrangler config should delete deployed cron schedules

• #​9245 b87b472 Thanks @​penalosa! - Support Mixed Mode Dispatch Namespaces

• Updated dependencies [db5ea8f, b87b472]:

  • [email protected]

---

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.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[github-actions]

Apollo Federation Subgraph Compatibility Results

Federation 1 Support	Federation 2 Support
_service 🟢 @key (single) 🟢 @key (multi) 🟢 @key (composite) 🟢 repeatable @key 🟢 @requires 🟢 @provides 🟢 federated tracing 🟢	@link 🟢 @shareable 🟢 @tag 🟢 @override 🟢 @inaccessible 🟢 @composeDirective 🟢 @interfaceObject 🟢

Learn more:

• Apollo Federation Subgraph Specification
• Compatibility Tests

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://pr-4042.graphql-yoga.pages.dev

[github-actions]

✅ Benchmark Results

     ✓ no_errors{mode:graphql}
     ✓ expected_result{mode:graphql}
     ✓ no_errors{mode:graphql-jit}
     ✓ expected_result{mode:graphql-jit}
     ✓ no_errors{mode:graphql-response-cache}
     ✓ expected_result{mode:graphql-response-cache}
     ✓ no_errors{mode:graphql-no-parse-validate-cache}
     ✓ expected_result{mode:graphql-no-parse-validate-cache}
     ✓ no_errors{mode:uws}
     ✓ expected_result{mode:uws}

     checks.......................................: 100.00% ✓ 389978      ✗ 0     
     data_received................................: 1.6 GB  11 MB/s
     data_sent....................................: 78 MB   523 kB/s
     http_req_blocked.............................: avg=1.52µs   min=1.03µs   med=1.33µs   max=272.47µs p(90)=1.98µs   p(95)=2.17µs  
     http_req_connecting..........................: avg=3ns      min=0s       med=0s       max=150.19µs p(90)=0s       p(95)=0s      
     http_req_duration............................: avg=549.36µs min=355.19µs med=488.92µs max=19.03ms  p(90)=656.98µs p(95)=681.78µs
       { expected_response:true }.................: avg=549.36µs min=355.19µs med=488.92µs max=19.03ms  p(90)=656.98µs p(95)=681.78µs
     ✓ { mode:graphql-jit }.......................: avg=466.83µs min=355.19µs med=427.14µs max=19.03ms  p(90)=469.13µs p(95)=491.04µs
     ✓ { mode:graphql-no-parse-validate-cache }...: avg=699.46µs min=583.46µs med=654.25µs max=13.91ms  p(90)=695.33µs p(95)=725µs   
     ✓ { mode:graphql-response-cache }............: avg=528.6µs  min=415.37µs med=489.48µs max=12.24ms  p(90)=526.8µs  p(95)=542µs   
     ✓ { mode:graphql }...........................: avg=557.87µs min=422.24µs med=502.09µs max=18.82ms  p(90)=578.44µs p(95)=680.05µs
     ✓ { mode:uws }...............................: avg=530.1µs  min=413.38µs med=483.3µs  max=8.6ms    p(90)=528.3µs  p(95)=562.52µs
     http_req_failed..............................: 0.00%   ✓ 0           ✗ 194989
     http_req_receiving...........................: avg=34.58µs  min=16.92µs  med=33.95µs  max=2.76ms   p(90)=40.02µs  p(95)=43.6µs  
     http_req_sending.............................: avg=8.91µs   min=5.8µs    med=7.85µs   max=5.42ms   p(90)=11.37µs  p(95)=12.69µs 
     http_req_tls_handshaking.....................: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting.............................: avg=505.86µs min=329.71µs med=446.28µs max=18.91ms  p(90)=613.06µs p(95)=636.2µs 
     http_reqs....................................: 194989  1299.914013/s
     iteration_duration...........................: avg=764.14µs min=547.84µs med=699.31µs max=19.52ms  p(90)=873.39µs p(95)=903.32µs
     iterations...................................: 194989  1299.914013/s
     vus..........................................: 1       min=1         max=2   
     vus_max......................................: 2       min=2         max=2