Skip to content

chore(deps-dev)(deps-dev): Bump the dev-deps group across 1 directory with 10 updates#710

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/main/dev-deps-bbfe085a27
Open

chore(deps-dev)(deps-dev): Bump the dev-deps group across 1 directory with 10 updates#710
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/main/dev-deps-bbfe085a27

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Jun 3, 2026

Bumps the dev-deps group with 10 updates in the / directory:

Package From To
@biomejs/biome 2.4.15 2.4.16
@vitest/coverage-v8 4.1.6 4.1.7
skills 1.5.7 1.5.9
turbo 2.9.14 2.9.15
@cloudflare/workers-types 4.20260515.1 4.20260524.1
wrangler 4.91.0 4.94.0
@types/react 19.2.14 19.2.15
@cloudflare/vitest-pool-workers 0.16.6 0.16.10
@prisma/compute-sdk 0.17.0 0.18.0
@prisma/management-api-sdk 1.29.0 1.32.0

Updates @biomejs/biome from 2.4.15 to 2.4.16

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.4.16

2.4.16

Patch Changes

  • #10329 ef764d5 Thanks @​Conaclos! - Fixed an issue where diagnostics showed an incorrect location in Astro files.

  • #10363 50aa415 Thanks @​dyc3! - Fixed HTML formatting for a case where comments could cause the formatter to split up a closing tag, which would cause the resulting HTML to be syntactically invalid.

    Input:

    <span
  ><!-- 1
--><span>a</span
  ><!-- 2
--><span>b</span
  ><!-- 3
--></span>

    Output:

      <span
	  ><!-- 1
- --> <span>a</span<!-- 2
- --> ><span>b</span><!-- 3
+ --><span>a</span><!-- 2
+ --><span>b</span><!-- 3
  --></span
  >

  • #10465 0c718da Thanks @​dfedoryshchev! - Fixed diagnostics emitted by the noUntrustedLicenses rule.

  • #10358 05c2617 Thanks @​dyc3! - Fixed #10356: biome rage --linter now displays rules enabled through linter domains in the enabled rules list.

  • #10300 950247c Thanks @​dyc3! - Fixed #10265: Svelte function bindings such as bind:value={get, set} are now parsed more precisely, so noCommaOperator won't emit false positives for that syntax anymore.

  • #9786 e71f584 Thanks @​MeGaNeKoS! - Fixed #8480: useDestructuring now provides variableDeclarator and assignmentExpression options to control which contexts enforce destructuring, matching ESLint's prefer-destructuring configuration. Both default to {array: true, object: true}. The diagnostic for object destructuring in assignment expressions now instructs users to wrap the assignment in parentheses.

  • #10425 1948b72 Thanks @​sjh9714! - Fixed #10244: The useOptionalChain rule now detects negated guard inequality chains like !foo || foo.bar !== "x".

  • #10442 001f94f Thanks @​ematipico! - Fixed #10411: noMisusedPromises no longer causes a stack overflow when a nested function returns an object with shorthand properties that shadow destructured variables from an outer scope.

  • #10318 9b1577f Thanks @​dyc3! - Added support for formatter.trailingCommas in overrides. This option was previously available in the top-level formatter configuration but missing from formatter overrides.

  • #10319 2e37709 Thanks @​dyc3! - Fixed Vue and Svelte formatting for standalone interpolations in inline elements. Biome now preserves existing newlines in cases like:

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.4.16

Patch Changes

  • #10329 ef764d5 Thanks @​Conaclos! - Fixed an issue where diagnostics showed an incorrect location in Astro files.

  • #10363 50aa415 Thanks @​dyc3! - Fixed HTML formatting for a case where comments could cause the formatter to split up a closing tag, which would cause the resulting HTML to be syntactically invalid.

    Input:

    <span
  ><!-- 1
--><span>a</span
  ><!-- 2
--><span>b</span
  ><!-- 3
--></span>

    Output:

      <span
	  ><!-- 1
- --> <span>a</span<!-- 2
- --> ><span>b</span><!-- 3
+ --><span>a</span><!-- 2
+ --><span>b</span><!-- 3
  --></span
  >

  • #10465 0c718da Thanks @​dfedoryshchev! - Fixed diagnostics emitted by the noUntrustedLicenses rule.

  • #10358 05c2617 Thanks @​dyc3! - Fixed #10356: biome rage --linter now displays rules enabled through linter domains in the enabled rules list.

  • #10300 950247c Thanks @​dyc3! - Fixed #10265: Svelte function bindings such as bind:value={get, set} are now parsed more precisely, so noCommaOperator won't emit false positives for that syntax anymore.

  • #9786 e71f584 Thanks @​MeGaNeKoS! - Fixed #8480: useDestructuring now provides variableDeclarator and assignmentExpression options to control which contexts enforce destructuring, matching ESLint's prefer-destructuring configuration. Both default to {array: true, object: true}. The diagnostic for object destructuring in assignment expressions now instructs users to wrap the assignment in parentheses.

  • #10425 1948b72 Thanks @​sjh9714! - Fixed #10244: The useOptionalChain rule now detects negated guard inequality chains like !foo || foo.bar !== "x".

  • #10442 001f94f Thanks @​ematipico! - Fixed #10411: noMisusedPromises no longer causes a stack overflow when a nested function returns an object with shorthand properties that shadow destructured variables from an outer scope.

  • #10318 9b1577f Thanks @​dyc3! - Added support for formatter.trailingCommas in overrides. This option was previously available in the top-level formatter configuration but missing from formatter overrides.

  • #10319 2e37709 Thanks @​dyc3! - Fixed Vue and Svelte formatting for standalone interpolations in inline elements. Biome now preserves existing newlines in cases like:

    

    • 






... (truncated)





Commits

    

  • 5f4ea56 ci: release (#10326)
    • 

  • de2a33c fix(core): regression in emitted types (#10478)
    • 

  • d835303 docs: remove redundant default phrase in useConsistentObjectDefinitions rul...
    • 

  • 4f1aaf2 fix: incorrect build when using build or test (#10426)
    • 

  • dc73b6b refactor: make plugins opt-in via feature gate (#10418)
    • 

  • e71f584 feat(useDestructuring): add options for assignment/declaration and improve di...
    • 

  • 9b1577f fix(config): support trailingCommas in overrides (#10318)
    • 

  • See full diff in compare view
    • 







Updates @vitest/coverage-v8 from 4.1.6 to 4.1.7



Release notes

Sourced from @​vitest/coverage-v8's releases.




v4.1.7


   🐞 Bug Fixes



    View changes on GitHub







Commits






Updates skills from 1.5.7 to 1.5.9



Release notes

Sourced from skills's releases.




v1.5.9


Changelog


    

  • Ignore vendored skills in packages, to prevent duplicate installations (#1281)
    • 



Contributors


@​quuu


v1.5.8


Changelog


    

  • feat: discover nested catalog skills in priority dirs by default (#1272)
    • 

  • feat: add Zed editor support (#1267)
    • 

  • Clean up skills deleted upstream on skills update (#1218)
    • 

  • fix: preserve ssh git urls in lock sources (#1098)
    • 



Contributors


@​evaisse,@​jasonnvidia @​quuu,@​swannysec







Commits






Updates turbo from 2.9.14 to 2.9.15



Release notes

Sourced from turbo's releases.




Turborepo v2.9.15



What's Changed


Changelog






... (truncated)





Commits






Updates @cloudflare/workers-types from 4.20260515.1 to 4.20260524.1



Commits






Updates wrangler from 4.91.0 to 4.94.0



Release notes

Sourced from wrangler's releases.




wrangler@4.94.0


Minor Changes


    

  • 

    #13897 52e9082 Thanks @​dario-piotrowicz! - Add automatic Cloudflare skills installation for AI coding agents
    

    Wrangler now detects AI coding agents and offers to install Cloudflare skill files from the cloudflare/skills GitHub repository. Users are prompted once interactively; subsequent runs skip the prompt. Use --install-skills to install without prompting.
    

    • 

  • 

    #13989 f598eac Thanks @​MattieTK! - Print a QR code alongside the tunnel URL when sharing via Cloudflare Tunnel
    

    When a tunnel is started (via wrangler dev --tunnel or the Vite plugin with tunnel: true), a scannable QR code is now printed to the terminal beneath the tunnel URL. This makes it easy to open the tunnel on a mobile device without manually copying the URL.
    

    The QR code uses Unicode block characters for a compact representation and is generated best-effort -- if generation fails for any reason, the tunnel URL is still displayed as before.
    

    • 

  • 

    #13467 3a1fbed Thanks @​deloreyj! - Add schedule property to Workflow bindings for cron-based triggering
    

    

    Note: This is a configuration-only change. Scheduled triggering of Workflow instances is not yet available — adding schedule to a Workflow binding will not result in scheduled invocations at this time. This change lays the groundwork for an upcoming feature.
    

    

    Workflow bindings in wrangler.json now accept an optional schedule field that configures one or more cron expressions to automatically trigger new workflow instances on a schedule.
    

    // wrangler.json
{
  "workflows": [
    {
      "binding": "MY_WORKFLOW",
      "name": "my-workflow",
      "class_name": "MyWorkflow",
      "schedule": "0 9 * * 1"
    }
  ]
}
    

    Multiple schedules can be provided as an array:
    

    {
  "workflows": [
    {
      "binding": "MY_WORKFLOW",
      "name": "my-workflow",
      "class_name": "MyWorkflow",
      "schedule": ["0 9 * * 1", "0 17 * * 5"]
    }
  ]
}
    

    The schedule is sent to the Workflows control plane on wrangler deploy. Configuring schedule on a workflow binding that references an external script_name is an error — the schedule must be configured on the worker that defines the workflow.
    

    • 






... (truncated)





Commits

    

  • b92f87c Version Packages (#13995)
    • 

  • fc1f7b9 [wrangler] Fix Access Service Token authentication for service-auth-only apps...
    • 

  • f598eac [wrangler][vite-plugin] Print QR code for tunnel URLs (#13989)
    • 

  • 52e9082 Add automatic Cloudflare skills installation for AI coding agents (#13897)
    • 

  • 0733688 build(deps): bump the workerd-and-workers-types group with 2 updates (#13993)
    • 

  • 8c569c6 [wrangler] Include column names in D1 SQL export (#12277)
    • 

  • 3a1fbed [wrangler] Add schedule property to Workflow bindings for cron-based triggeri...
    • 

  • 90092c0 [vitest-pool-workers] Stop externalizing devDependencies from the published b...
    • 

  • 5ee65d5 Version Packages (#13969)
    • 

  • e04e180 [wrangler] Improve asset upload retry log message (#13990)
    • 

  • Additional commits viewable in compare view
    • 







Updates @types/react from 19.2.14 to 19.2.15



Commits






Updates @cloudflare/vitest-pool-workers from 0.16.6 to 0.16.10



Release notes

Sourced from @​cloudflare/vitest-pool-workers's releases.




@​cloudflare/vitest-pool-workers@​0.16.10


Patch Changes



@​cloudflare/vitest-pool-workers@​0.16.9


Patch Changes


    

  • 

    #13933 90092c0 Thanks @​petebacondarwin! - Derive bundler externals from package.json and shrink the published bundle
    

    The bundler's external list was previously hand-maintained and out of sync with package.json — undici and semver were both listed as external despite being only devDependencies. The published dist/pool/index.mjs consequently contained a top-level import { fetch } from "undici" that was only resolvable because pnpm happened to hoist undici from other packages' devDependencies during local development.
    

    The bundler now derives its external list from dependencies + peerDependencies in package.json, making it impossible for a devDependency to silently end up externalized.
    

    Combined with the new "sideEffects": false declaration in @cloudflare/workers-utils, the unused cloudflared / tunnel exports (and their transitive undici import) are now tree-shaken out of the pool entirely. dist/pool/index.mjs no longer references undici at all, and shrinks from ~489 KB to ~125 KB.
    

    • 

  • 

    Updated dependencies [52e9082, 0733688, fc1f7b9, 30657e1, 8c569c6, f598eac, 3a1fbed]:
    

      

    • wrangler@4.94.0
      • 

    • miniflare@4.20260521.0
      • 

    

    • 



@​cloudflare/vitest-pool-workers@​0.16.8


Patch Changes


    

  • 

    #13919 c7eab7f Thanks @​petebacondarwin! - Fix the outbound CF-Worker header reflecting the route pattern hostname instead of the parent zone, and falling back to <worker-name>.example.com under vite dev, vitest-pool-workers, and getPlatformProxy
    

    Two related issues affected the CF-Worker header on outbound subrequests in local development:
    

      

    1. Under @cloudflare/vite-plugin, @cloudflare/vitest-pool-workers, and getPlatformProxy, the header fell back to <worker-name>.example.com even when routes were configured, because unstable_getMiniflareWorkerOptions and the equivalent getPlatformProxy worker-options path did not propagate a zone value to Miniflare. This broke local development against services that reject unknown CF-Worker hosts (for example, Apple WeatherKit returns 403 Forbidden).
      2. 

    2. Across the above paths and wrangler dev --local, when a route used the zone_name field (for example { pattern: "foo.example.com/*", zone_name: "example.com" }), the header was set to the pattern's hostname (foo.example.com) rather than the zone name (example.com). Production sets CF-Worker to the zone name that owns the Worker, so this was inconsistent with deployed behaviour.
      3. 

    

    Both bugs are fixed: the new unstable_getMiniflareWorkerOptions / getPlatformProxy path now propagates a zone derived from the first configured route, and all four local-dev paths now prefer a route's explicit zone_name over the pattern hostname when computing that zone. When zone_name isn't set, the existing best-effort behaviour is preserved — for wrangler dev this means dev.host is still honoured as a local override and the pattern hostname is used as a final fallback. Resolving the parent zone for zone_id-only, custom_domain, or plain-string routes would require an API lookup, so locally we still approximate it with the pattern hostname.
    

    Note: dev.host is intentionally not consulted by the unstable_getMiniflareWorkerOptions / getPlatformProxy paths — the dev config block is specific to wrangler dev.
    

    • 

  • 

    Updated dependencies [fa1f61f, 2679e05, 7e40d98, adc9221, 735852d, d803737, c7eab7f, e04e180, 59cd880, 62abf97, e8c2031, e349fe0, da0fa8c, a5c9365]:
    

      

    • miniflare@4.20260520.0
      • 

    • wrangler@4.93.1
      • 

    

    • 



@​cloudflare/vitest-pool-workers@​0.16.7


Patch Changes


    

  • 

    #13961 2cb658c Thanks @​threepointone! - Preserve same-stub RPC call order for wrapped Worker and Durable Object entrypoints
    

    Previously, dynamically wrapped RPC methods could resolve and invoke out of order when many calls were fired without awaiting each individual call. This now queues method resolution per wrapper instance so calls begin in the order they were received.
    

    • 

  • 

    Updated dependencies [aac7ca0, b25dc0d, ae047ee, a4f22bc, f78d435, aac7ca0, c5c9e20, ebf4b24, b27eb18, 895baf5, 7bcdf45]:
    

      

    • wrangler@4.93.0
      • 

    • miniflare@4.20260518.0
      • 

    

    • 








Changelog

Sourced from @​cloudflare/vitest-pool-workers's changelog.




0.16.10


Patch Changes



0.16.9


Patch Changes


    

  • 

    #13933 90092c0 Thanks @​petebacondarwin! - Derive bundler externals from package.json and shrink the published bundle
    

    The bundler's external list was previously hand-maintained and out of sync with package.json — undici and semver were both listed as external despite being only devDependencies. The published dist/pool/index.mjs consequently contained a top-level import { fetch } from "undici" that was only resolvable because pnpm happened to hoist undici from other packages' devDependencies during local development.
    

    The bundler now derives its external list from dependencies + peerDependencies in package.json, making it impossible for a devDependency to silently end up externalized.
    

    Combined with the new "sideEffects": false declaration in @cloudflare/workers-utils, the unused cloudflared / tunnel exports (and their transitive undici import) are now tree-shaken out of the pool entirely. dist/pool/index.mjs no longer references undici at all, and shrinks from ~489 KB to ~125 KB.
    

    • 

  • 

    Updated dependencies [52e9082, 0733688, fc1f7b9, 30657e1, 8c569c6, f598eac, 3a1fbed]:
    

      

    • wrangler@4.94.0
      • 

    • miniflare@4.20260521.0
      • 

    

    • 



0.16.8


Patch Changes


    

  • 

    #13919 c7eab7f Thanks @​petebacondarwin! - Fix the outbound CF-Worker header reflecting the route pattern hostname instead of the parent zone, and falling back to <worker-name>.example.com under vite dev, vitest-pool-workers, and getPlatformProxy
    

    Two related issues affected the CF-Worker header on outbound subrequests in local development:
    

      

    1. Under @cloudflare/vite-plugin, @cloudflare/vitest-pool-workers, and getPlatformProxy, the header fell back to <worker-name>.example.com even when routes were configured, because unstable_getMiniflareWorkerOptions and the equivalent getPlatformProxy worker-options path did not propagate a zone value to Miniflare. This broke local development against services that reject unknown CF-Worker hosts (for example, Apple WeatherKit returns 403 Forbidden).
      2. 

    2. Across the above paths and wrangler dev --local, when a route used the zone_name field (for example { pattern: "foo.example.com/*", zone_name: "example.com" }), the header was set to the pattern's hostname (foo.example.com) rather than the zone name (example.com). Production sets CF-Worker to the zone name that owns the Worker, so this was inconsistent with deployed behaviour.
      3. 

    

    Both bugs are fixed: the new unstable_getMiniflareWorkerOptions / getPlatformProxy path now propagates a zone derived from the first configured route, and all four local-dev paths now prefer a route's explicit zone_name over the pattern hostname when computing that zone. When zone_name isn't set, the existing best-effort behaviour is preserved — for wrangler dev this means dev.host is still honoured as a local override and the pattern hostname is used as a final fallback. Resolving the parent zone for zone_id-only, custom_domain, or plain-string routes would require an API lookup, so locally we still approximate it with the pattern hostname.
    

    Note: dev.host is intentionally not consulted by the unstable_getMiniflareWorkerOptions / getPlatformProxy paths — the dev config block is specific to wrangler dev.
    

    • 

  • 

    Updated dependencies [fa1f61f, 2679e05, 7e40d98, adc9221, 735852d, d803737, c7eab7f, e04e180, 59cd880, 62abf97, e8c2031, e349fe0, da0fa8c, a5c9365]:
    

      

    • miniflare@4.20260520.0
      • 

    • wrangler@4.93.1
      • 

    

    • 



0.16.7


Patch Changes


    

  • 

    #13961 2cb658c Thanks @​threepointone! - Preserve same-stub RPC call order for wrapped Worker and Durable Object entrypoints
    

    Previously, dynamically wrapped RPC methods could resolve and invoke out of order when many calls were fired without awaiting each individual call. This now queues method resolution per wrapper instance so calls begin in the order they were received.
    

    • 






... (truncated)





Commits

    

  • 0998725 Set disallowTypeAnnotations to false in `@typescript-eslint/consistent-ty...
    • 

  • 3a746ac [tools] Lint that all non-bundled deps of published packages are pinned (#14112)
    • 

  • 337e912 Remove trailing periods from URLs in terminal output (#14105)
    • 

  • 50ef724 Version Packages (#14082)
    • 

  • e3c862a Revert "Version Packages" (#14087)
    • 

  • 689f381 Version Packages (#14048)
    • 

  • 96ae856 [vitest-pool-workers] Dispatch RPC methods through proxied Durable Object ins...
    • 

  • 62dd39c Version Packages (#14012)
    • 

  • b92f87c Version Packages (#13995)
    • 

  • 90092c0 [vitest-pool-workers] Stop externalizing devDependencies from the published b...
    • 

  • Additional commits viewable in compare view
    • 







Updates @prisma/compute-sdk from 0.17.0 to 0.18.0



Commits






Updates @prisma/management-api-sdk from 1.29.0 to 1.32.0



Commits






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 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 s...
    • 



Description has been truncated

    

  
  



      


          

          
  
  

    
  
    
    

  

  

  



                    

          
        





  





    



      

  
        

  

      

  
  

  
          

  

    

      


  

      
        @dependabot
  




      

        
          chore(deps-dev)(deps-dev): Bump the dev-deps group across 1 directory…
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          4048f2b
        
      

    

  

    

      
… with 10 updates

Bumps the dev-deps group with 10 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) | `2.4.15` | `2.4.16` |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `4.1.6` | `4.1.7` |
| [skills](https://github.com/vercel-labs/skills) | `1.5.7` | `1.5.9` |
| [turbo](https://github.com/vercel/turborepo) | `2.9.14` | `2.9.15` |
| [@cloudflare/workers-types](https://github.com/cloudflare/workerd) | `4.20260515.1` | `4.20260524.1` |
| [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) | `4.91.0` | `4.94.0` |
| [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) | `19.2.14` | `19.2.15` |
| [@cloudflare/vitest-pool-workers](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/vitest-pool-workers) | `0.16.6` | `0.16.10` |
| [@prisma/compute-sdk](https://github.com/prisma/project-compute) | `0.17.0` | `0.18.0` |
| [@prisma/management-api-sdk](https://github.com/prisma/pdp-control-plane/tree/HEAD/packages/management-api-sdk) | `1.29.0` | `1.32.0` |



Updates `@biomejs/biome` from 2.4.15 to 2.4.16
- [Release notes](https://github.com/biomejs/biome/releases)
- [Changelog](https://github.com/biomejs/biome/blob/main/packages/@biomejs/biome/CHANGELOG.md)
- [Commits](https://github.com/biomejs/biome/commits/@biomejs/biome@2.4.16/packages/@biomejs/biome)

Updates `@vitest/coverage-v8` from 4.1.6 to 4.1.7
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.7/packages/coverage-v8)

Updates `skills` from 1.5.7 to 1.5.9
- [Release notes](https://github.com/vercel-labs/skills/releases)
- [Commits](vercel-labs/skills@v1.5.7...v1.5.9)

Updates `turbo` from 2.9.14 to 2.9.15
- [Release notes](https://github.com/vercel/turborepo/releases)
- [Changelog](https://github.com/vercel/turborepo/blob/main/RELEASE.md)
- [Commits](vercel/turborepo@v2.9.14...v2.9.15)

Updates `@cloudflare/workers-types` from 4.20260515.1 to 4.20260524.1
- [Release notes](https://github.com/cloudflare/workerd/releases)
- [Changelog](https://github.com/cloudflare/workerd/blob/main/RELEASE.md)
- [Commits](https://github.com/cloudflare/workerd/commits)

Updates `wrangler` from 4.91.0 to 4.94.0
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.94.0/packages/wrangler)

Updates `@types/react` from 19.2.14 to 19.2.15
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react)

Updates `@cloudflare/vitest-pool-workers` from 0.16.6 to 0.16.10
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/vitest-pool-workers/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/@cloudflare/vitest-pool-workers@0.16.10/packages/vitest-pool-workers)

Updates `@prisma/compute-sdk` from 0.17.0 to 0.18.0
- [Commits](https://github.com/prisma/project-compute/commits)

Updates `@prisma/management-api-sdk` from 1.29.0 to 1.32.0
- [Commits](https://github.com/prisma/pdp-control-plane/commits/HEAD/packages/management-api-sdk)

---
updated-dependencies:
- dependency-name: "@biomejs/biome"
  dependency-version: 2.4.16
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-deps
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 4.1.7
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-deps
- dependency-name: skills
  dependency-version: 1.5.9
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-deps
- dependency-name: turbo
  dependency-version: 2.9.15
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-deps
- dependency-name: "@cloudflare/workers-types"
  dependency-version: 4.20260524.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-deps
- dependency-name: wrangler
  dependency-version: 4.94.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-deps
- dependency-name: "@types/react"
  dependency-version: 19.2.15
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-deps
- dependency-name: "@cloudflare/vitest-pool-workers"
  dependency-version: 0.16.10
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-deps
- dependency-name: "@prisma/compute-sdk"
  dependency-version: 0.18.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-deps
- dependency-name: "@prisma/management-api-sdk"
  dependency-version: 1.32.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-deps
...

Signed-off-by: dependabot[bot] <support@github.com>

    







  








      

  
            

    

      
    

    


      


          @dependabot
dependabot
Bot



          added
  the 

  dependencies

  Pull requests that update a dependency file
 label


      Jun 3, 2026

    

  



  

  
  

  
      @dependabot
  dependabot
Bot

          requested a review
  from a team
    as a code owner


    June 3, 2026 12:47    
    









      

  
      



  

  @pkg-pr-new






  



    

      

  

    

      

          
    
    

  


        
            
  
      
              Copy link

  

              
  
      
                Copy Markdown

  

        
      

    


    

        



        

    

  


  

    

      
          
      

      
            pkg-pr-new
  Bot

      

      

      commented


        Jun 3, 2026



      
    


  





      


        



  
    

      
          
Open in StackBlitz


@prisma-next/extension-author-tools


npm i https://pkg.pr.new/@prisma-next/extension-author-tools@710





@prisma-next/mongo-runtime


npm i https://pkg.pr.new/@prisma-next/mongo-runtime@710





@prisma-next/family-mongo


npm i https://pkg.pr.new/@prisma-next/family-mongo@710





@prisma-next/sql-runtime


npm i https://pkg.pr.new/@prisma-next/sql-runtime@710





@prisma-next/family-sql


npm i https://pkg.pr.new/@prisma-next/family-sql@710





@prisma-next/extension-arktype-json


npm i https://pkg.pr.new/@prisma-next/extension-arktype-json@710





@prisma-next/middleware-cache


npm i https://pkg.pr.new/@prisma-next/middleware-cache@710





@prisma-next/mongo


npm i https://pkg.pr.new/@prisma-next/mongo@710





@prisma-next/extension-paradedb


npm i https://pkg.pr.new/@prisma-next/extension-paradedb@710





@prisma-next/extension-pgvector


npm i https://pkg.pr.new/@prisma-next/extension-pgvector@710





@prisma-next/extension-postgis


npm i https://pkg.pr.new/@prisma-next/extension-postgis@710





@prisma-next/postgres


npm i https://pkg.pr.new/@prisma-next/postgres@710





@prisma-next/sql-orm-client


npm i https://pkg.pr.new/@prisma-next/sql-orm-client@710





@prisma-next/sqlite


npm i https://pkg.pr.new/@prisma-next/sqlite@710





@prisma-next/target-mongo


npm i https://pkg.pr.new/@prisma-next/target-mongo@710





@prisma-next/adapter-mongo


npm i https://pkg.pr.new/@prisma-next/adapter-mongo@710





@prisma-next/driver-mongo


npm i https://pkg.pr.new/@prisma-next/driver-mongo@710





@prisma-next/contract


npm i https://pkg.pr.new/@prisma-next/contract@710





@prisma-next/utils


npm i https://pkg.pr.new/@prisma-next/utils@710





@prisma-next/config


npm i https://pkg.pr.new/@prisma-next/config@710





@prisma-next/errors


npm i https://pkg.pr.new/@prisma-next/errors@710





@prisma-next/framework-components


npm i https://pkg.pr.new/@prisma-next/framework-components@710





@prisma-next/operations


npm i https://pkg.pr.new/@prisma-next/operations@710





@prisma-next/ts-render


npm i https://pkg.pr.new/@prisma-next/ts-render@710





@prisma-next/contract-authoring


npm i https://pkg.pr.new/@prisma-next/contract-authoring@710





@prisma-next/ids


npm i https://pkg.pr.new/@prisma-next/ids@710





@prisma-next/psl-parser


npm i https://pkg.pr.new/@prisma-next/psl-parser@710





@prisma-next/psl-printer


npm i https://pkg.pr.new/@prisma-next/psl-printer@710





@prisma-next/cli


npm i https://pkg.pr.new/@prisma-next/cli@710





@prisma-next/cli-telemetry


npm i https://pkg.pr.new/@prisma-next/cli-telemetry@710





@prisma-next/emitter


npm i https://pkg.pr.new/@prisma-next/emitter@710





@prisma-next/migration-tools


npm i https://pkg.pr.new/@prisma-next/migration-tools@710





prisma-next


npm i https://pkg.pr.new/prisma-next@710





@prisma-next/vite-plugin-contract-emit


npm i https://pkg.pr.new/@prisma-next/vite-plugin-contract-emit@710





@prisma-next/mongo-codec


npm i https://pkg.pr.new/@prisma-next/mongo-codec@710





@prisma-next/mongo-contract


npm i https://pkg.pr.new/@prisma-next/mongo-contract@710





@prisma-next/mongo-value


npm i https://pkg.pr.new/@prisma-next/mongo-value@710





@prisma-next/mongo-contract-psl


npm i https://pkg.pr.new/@prisma-next/mongo-contract-psl@710





@prisma-next/mongo-contract-ts


npm i https://pkg.pr.new/@prisma-next/mongo-contract-ts@710





@prisma-next/mongo-emitter


npm i https://pkg.pr.new/@prisma-next/mongo-emitter@710





@prisma-next/mongo-schema-ir


npm i https://pkg.pr.new/@prisma-next/mongo-schema-ir@710





@prisma-next/mongo-query-ast


npm i https://pkg.pr.new/@prisma-next/mongo-query-ast@710





@prisma-next/mongo-orm


npm i https://pkg.pr.new/@prisma-next/mongo-orm@710





@prisma-next/mongo-query-builder


npm i https://pkg.pr.new/@prisma-next/mongo-query-builder@710





@prisma-next/mongo-lowering


npm i https://pkg.pr.new/@prisma-next/mongo-lowering@710





@prisma-next/mongo-wire


npm i https://pkg.pr.new/@prisma-next/mongo-wire@710





@prisma-next/sql-contract


npm i https://pkg.pr.new/@prisma-next/sql-contract@710





@prisma-next/sql-errors


npm i https://pkg.pr.new/@prisma-next/sql-errors@710





@prisma-next/sql-operations


npm i https://pkg.pr.new/@prisma-next/sql-operations@710





@prisma-next/sql-schema-ir


npm i https://pkg.pr.new/@prisma-next/sql-schema-ir@710





@prisma-next/sql-contract-psl


npm i https://pkg.pr.new/@prisma-next/sql-contract-psl@710





@prisma-next/sql-contract-ts


npm i https://pkg.pr.new/@prisma-next/sql-contract-ts@710





@prisma-next/sql-contract-emitter


npm i https://pkg.pr.new/@prisma-next/sql-contract-emitter@710





@prisma-next/sql-lane-query-builder


npm i https://pkg.pr.new/@prisma-next/sql-lane-query-builder@710





@prisma-next/sql-relational-core


npm i https://pkg.pr.new/@prisma-next/sql-relational-core@710





@prisma-next/sql-builder


npm i https://pkg.pr.new/@prisma-next/sql-builder@710





@prisma-next/target-postgres


npm i https://pkg.pr.new/@prisma-next/target-postgres@710





@prisma-next/target-sqlite


npm i https://pkg.pr.new/@prisma-next/target-sqlite@710





@prisma-next/adapter-postgres


npm i https://pkg.pr.new/@prisma-next/adapter-postgres@710





@prisma-next/adapter-sqlite


npm i https://pkg.pr.new/@prisma-next/adapter-sqlite@710





@prisma-next/driver-postgres


npm i https://pkg.pr.new/@prisma-next/driver-postgres@710





@prisma-next/driver-sqlite


npm i https://pkg.pr.new/@prisma-next/driver-sqlite@710





commit: 4048f2b


      		
    

  





        


            

            
            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    












      

  
      



  

  @github-actions






  



    

      

  

    

      

          
    
    

  


        
            
  
      
              Copy link

  

              
  
      
                Copy Markdown

  

        
      

    


    

        



        

    

  


  

    

      
          
      

      
            github-actions
  Bot

      

      

      commented


        Jun 3, 2026



      
    


  





      


        



  
    

      
          
size-limit report 📦






Path
Size






postgres / no-emit
137.37 KB (0%)




postgres / emit
108.83 KB (0%)




mongo / no-emit
75.85 KB (0%)




mongo / emit
70.78 KB (0%)




cf-worker / no-emit
166.35 KB (0%)




cf-worker / emit
134.51 KB (0%)






      		
    

  





        


            

            
            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    
















  
  

    

      

  










  








  
      

  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment


  










      

  

    
    

    

  

    Reviewers
  


    

    No reviews






    

  


      
  

    Assignees
  



        


    No one assigned







      


  


  

    Labels
  



    

      

    dependencies

  Pull requests that update a dependency file








      

  

    

        

    Projects
  


        




    None yet




  



      


  

    
  

    Milestone
  


      No milestone





    
      
          


  

    

      
        

          
  

    Development
  



            


Successfully merging this pull request may close these issues.





  
  



      
    

  




      

    

  
        

  

    

      0 participants