Skip to content

chore(deps-dev): bump the dev-dependencies group across 1 directory with 7 updates#506

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dev-dependencies-c79fc1b8e2
Open

chore(deps-dev): bump the dev-dependencies group across 1 directory with 7 updates#506
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dev-dependencies-c79fc1b8e2

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

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

Bumps the dev-dependencies group with 7 updates in the / directory:

Package From To
@biomejs/biome 2.4.15 2.4.16
turbo 2.9.14 2.9.16
@prisma-next/cli 0.8.0 0.11.0
@prisma-next/psl-parser 0.8.0 0.11.0
@prisma-next/sql-contract-ts 0.8.0 0.11.0
@prisma-next/sql-schema-ir 0.8.0 0.11.0
@supabase/supabase-js 2.105.4 2.106.2

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 turbo from 2.9.14 to 2.9.16



Release notes

Sourced from turbo's releases.




Turborepo v2.9.16



What's Changed


Changelog



Full Changelog: vercel/turborepo@v2.9.15...v2.9.16


Turborepo v2.9.16-canary.2



What's Changed


Changelog



New Contributors



Full Changelog: vercel/turborepo@v2.9.15-canary.7...v2.9.16-canary.2


Turborepo v2.9.15






... (truncated)





Commits






Updates @prisma-next/cli from 0.8.0 to 0.11.0



Release notes

Sourced from @​prisma-next/cli's releases.




v0.11.0


What's Changed



New Contributors



Full Changelog: prisma/prisma-next@v0.10.0...v0.11.0


v0.10.0


What's Changed



Full Changelog: prisma/prisma-next@v0.9.0...v0.10.0


v0.9.0


What's Changed






... (truncated)





Changelog

Sourced from @​prisma-next/cli's changelog.




Changelog


The rolling, newest-first index of Prisma Next releases. Each entry mirrors the release's committed notes file under https://github.com/prisma/prisma-next/blob/main/docs/releases (the body of its GitHub Release) under a ## v<version> header — see https://github.com/prisma/prisma-next/blob/main/docs/releases/README.md for the convention and authoring template.


Changelog tracking starts at v0.12.0, the first release cut after this convention landed. For v0.11.0 and earlier, see the GitHub Releases page — historical notes are not backfilled here.



v0.13.0 (unreleased)


Breaking changes


    

  • 

    MTI variant tables materialize a base-PK link column (@prisma-next/sql-contract-psl) — a PSL @@base(Parent, "tag") variant that carries its own @@map (and is therefore stored in its own table) now emits a base-PK link column in storage: the variant table gains an id column, a single-column primary key on it, and a cascading foreign key (ON DELETE CASCADE) referencing the base table's primary key. Previously the variant table held only the variant-specific columns with no primary key and no link to its base. This changes the emitted contract.json / contract.d.ts and the contract's storageHash. Re-emit your contract, then plan and apply the matching migration to add the column, PK, and FK to your database. Variants that share the base table (no own @@map) are unaffected. See the migration recipe. (#669)
    

    Before (emitted contract.json, variant table bug):
    

    "bug": {
  "columns": {
    "severity": { "codecId": "pg/text@1", "nullable": false }
  }
}
    

    After:
    

    "bug": {
  "columns": {
    "id": { "codecId": "sql/char@1", "nullable": false },
    "severity": { "codecId": "pg/text@1", "nullable": false }
  },
  "primaryKey": { "columns": ["id"] },
  "foreignKeys": [
    {
      "name": "bug_id_fkey",
      "columns": ["id"],
      "references": { "table": "task", "columns": ["id"] },
      "onDelete": "cascade"
    }
  ]
}
    

    • 



Features


    

  • STI variants can declare their own fields (@prisma-next/sql-contract-psl) — a PSL @@base(Parent, "tag") variant with no own @@map (single-table inheritance) may now declare its own scalar fields. Each such field is materialized as a column on the shared base table (always nullable in storage, since the base table also holds sibling-variant rows), and the variant no longer emits a stray shadow table. Previously the variant's column was never added to the base table, so the contract failed to emit with references non-existent column. This is purely enabling: existing contracts re-emit identically. (#669)
    • 



v0.12.0





... (truncated)





Commits






Updates @prisma-next/psl-parser from 0.8.0 to 0.11.0



Release notes

Sourced from @​prisma-next/psl-parser's releases.




v0.11.0


What's Changed



New Contributors



Full Changelog: prisma/prisma-next@v0.10.0...v0.11.0


v0.10.0


What's Changed



Full Changelog: prisma/prisma-next@v0.9.0...v0.10.0


v0.9.0


What's Changed






... (truncated)





Changelog

Sourced from @​prisma-next/psl-parser's changelog.




Changelog


The rolling, newest-first index of Prisma Next releases. Each entry mirrors the release's committed notes file under https://github.com/prisma/prisma-next/blob/main/docs/releases (the body of its GitHub Release) under a ## v<version> header — see https://github.com/prisma/prisma-next/blob/main/docs/releases/README.md for the convention and authoring template.


Changelog tracking starts at v0.12.0, the first release cut after this convention landed. For v0.11.0 and earlier, see the GitHub Releases page — historical notes are not backfilled here.



v0.13.0 (unreleased)


Breaking changes


    

  • 

    MTI variant tables materialize a base-PK link column (@prisma-next/sql-contract-psl) — a PSL @@base(Parent, "tag") variant that carries its own @@map (and is therefore stored in its own table) now emits a base-PK link column in storage: the variant table gains an id column, a single-column primary key on it, and a cascading foreign key (ON DELETE CASCADE) referencing the base table's primary key. Previously the variant table held only the variant-specific columns with no primary key and no link to its base. This changes the emitted contract.json / contract.d.ts and the contract's storageHash. Re-emit your contract, then plan and apply the matching migration to add the column, PK, and FK to your database. Variants that share the base table (no own @@map) are unaffected. See the migration recipe. (#669)
    

    Before (emitted contract.json, variant table bug):
    

    "bug": {
  "columns": {
    "severity": { "codecId": "pg/text@1", "nullable": false }
  }
}
    

    After:
    

    "bug": {
  "columns": {
    "id": { "codecId": "sql/char@1", "nullable": false },
    "severity": { "codecId": "pg/text@1", "nullable": false }
  },
  "primaryKey": { "columns": ["id"] },
  "foreignKeys": [
    {
      "name": "bug_id_fkey",
      "columns": ["id"],
      "references": { "table": "task", "columns": ["id"] },
      "onDelete": "cascade"
    }
  ]
}
    

    • 



Features


    

  • STI variants can declare their own fields (@prisma-next/sql-contract-psl) — a PSL @@base(Parent, "tag") variant with no own @@map (single-table inheritance) may now declare its own scalar fields. Each such field is materialized as a column on the shared base table (always nullable in storage, since the base table also holds sibling-variant rows), and the variant no longer emits a stray shadow table. Previously the variant's column was never added to the base table, so the contract failed to emit with references non-existent column. This is purely enabling: existing contracts re-emit identically. (#669)
    • 



v0.12.0





... (truncated)





Commits






Updates @prisma-next/sql-contract-ts from 0.8.0 to 0.11.0



Release notes

Sourced from @​prisma-next/sql-contract-ts's releases.




v0.11.0


What's Changed



New Contributors



Full Changelog: prisma/prisma-next@v0.10.0...v0.11.0


v0.10.0


What's Changed



Full Changelog: prisma/prisma-next@v0.9.0...v0.10.0


v0.9.0


What's Changed






... (truncated)





Changelog

Sourced from @​prisma-next/sql-contract-ts's changelog.




Changelog


The rolling, newest-first index of Prisma Next releases. Each entry mirrors the release's committed notes file under https://github.com/prisma/prisma-next/blob/main/docs/releases (the body of its GitHub Release) under a ## v<version> header — see https://github.com/prisma/prisma-next/blob/main/docs/releases/README.md for the convention and authoring template.


Changelog tracking starts at v0.12.0, the first release cut after this convention landed. For v0.11.0 and earlier, see the GitHub Releases page — historical notes are not backfilled here.



v0.13.0 (unreleased)


Breaking changes


    

  • 

    MTI variant tables materialize a base-PK link column (@prisma-next/sql-contract-psl) — a PSL @@base(Parent, "tag") variant that carries its own @@map (and is therefore stored in its own table) now emits a base-PK link column in storage: the variant table gains an id column, a single-column primary key on it, and a cascading foreign key (ON DELETE CASCADE) referencing the base table's primary key. Previously the variant table held only the variant-specific columns with no primary key and no link to its base. This changes the emitted contract.json / contract.d.ts and the contract's storageHash. Re-emit your contract, then plan and apply the matching migration to add the column, PK, and FK to your database. Variants that share the base table (no own @@map) are unaffected. See the migration recipe. (#669)
    

    Before (emitted contract.json, variant table bug):
    

    "bug": {
  "columns": {
    "severity": { "codecId": "pg/text@1", "nullable": false }
  }
}
    

    After:
    

    "bug": {
  "columns": {
    "id": { "codecId": "sql/char@1", "nullable": false },
    "severity": { "codecId": "pg/text@1", "nullable": false }
  },
  "primaryKey": { "columns": ["id"] },
  "foreignKeys": [
    {
      "name": "bug_id_fkey",
      "columns": ["id"],
      "references": { "table": "task", "columns": ["id"] },
      "onDelete": "cascade"
    }
  ]
}
    

    • 



Features


    

  • STI variants can declare their own fields (@prisma-next/sql-contract-psl) — a PSL @@base(Parent, "tag") variant with no own @@map (single-table inheritance) may now declare its own scalar fields. Each such field is materialized as a column on the shared base table (always nullable in storage, since the base table also holds sibling-variant rows), and the variant no longer emits a stray shadow table. Previously the variant's column was never added to the base table, so the contract failed to emit with references non-existent column. This is purely enabling: existing contracts re-emit identically. (#669)
    • 



v0.12.0





... (truncated)





Commits






Updates @prisma-next/sql-schema-ir from 0.8.0 to 0.11.0



Release notes

Sourced from 

    

  
  



      


          

          
  
  

    
  
    
    

  

  

  



                    

          
        





  





    



      

  
        

  

      

  
  

  
          

  

    

      


  

      
        @dependabot
  




      

        
          chore(deps-dev): bump the dev-dependencies group across 1 directory w…
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          81a7786
        
      

    

  

    

      
…ith 7 updates

Bumps the dev-dependencies group with 7 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` |
| [turbo](https://github.com/vercel/turborepo) | `2.9.14` | `2.9.16` |
| [@prisma-next/cli](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/3-tooling/cli) | `0.8.0` | `0.11.0` |
| [@prisma-next/psl-parser](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/2-authoring/psl-parser) | `0.8.0` | `0.11.0` |
| [@prisma-next/sql-contract-ts](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/2-authoring/contract-ts) | `0.8.0` | `0.11.0` |
| [@prisma-next/sql-schema-ir](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/1-core/schema-ir) | `0.8.0` | `0.11.0` |
| [@supabase/supabase-js](https://github.com/supabase/supabase-js/tree/HEAD/packages/core/supabase-js) | `2.105.4` | `2.106.2` |



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 `turbo` from 2.9.14 to 2.9.16
- [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.16)

Updates `@prisma-next/cli` from 0.8.0 to 0.11.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.11.0/packages/1-framework/3-tooling/cli)

Updates `@prisma-next/psl-parser` from 0.8.0 to 0.11.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.11.0/packages/1-framework/2-authoring/psl-parser)

Updates `@prisma-next/sql-contract-ts` from 0.8.0 to 0.11.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.11.0/packages/2-sql/2-authoring/contract-ts)

Updates `@prisma-next/sql-schema-ir` from 0.8.0 to 0.11.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.11.0/packages/2-sql/1-core/schema-ir)

Updates `@supabase/supabase-js` from 2.105.4 to 2.106.2
- [Release notes](https://github.com/supabase/supabase-js/releases)
- [Changelog](https://github.com/supabase/supabase-js/blob/master/packages/core/supabase-js/CHANGELOG.md)
- [Commits](https://github.com/supabase/supabase-js/commits/v2.106.2/packages/core/supabase-js)

---
updated-dependencies:
- dependency-name: "@biomejs/biome"
  dependency-version: 2.4.16
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: turbo
  dependency-version: 2.9.16
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: "@prisma-next/cli"
  dependency-version: 0.11.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: "@prisma-next/psl-parser"
  dependency-version: 0.11.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: "@prisma-next/sql-contract-ts"
  dependency-version: 0.11.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: "@prisma-next/sql-schema-ir"
  dependency-version: 0.11.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: "@supabase/supabase-js"
  dependency-version: 2.106.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
...

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

    







  








      

  
      



  

  @dependabot


    @github




  



    

      

  

    

      

          
    
    

  


        
            
  
      
              Copy link

  

              
  
      
                Copy Markdown

  

        
      

    


    

        

  
    Contributor


        

  Author


    

  


  

    

      
          
      

      
            dependabot
  Bot

      

      

      commented

        on behalf of github

        Jun 7, 2026



      
    


  





      


        



  
    

      
          
Labels


The following labels could not be found: supply-chain. Please create it before Dependabot can add it to a pull request.


Please fix the above issues or remove invalid values from dependabot.yml.


      		
    

  





        


            

            
            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    












      

  
            

    

      
    

    


      


          @dependabot
dependabot
Bot



          added
  the 

  dependencies

  Pull requests that update a dependency file
 label


      Jun 7, 2026

    

  



  

  
  

  
      @dependabot
  dependabot
Bot

          requested a review
  from a team
    as a code owner


    June 7, 2026 22:07    
    




    

    

      
    

    


      


          @dependabot
dependabot
Bot



          added
  the 

  dependencies

  Pull requests that update a dependency file
 label


      Jun 7, 2026

    

  








      

  
      



  

  @changeset-bot






  



    

      

  

    

      

          
    
    

  


        
            
  
      
              Copy link

  

              
  
      
                Copy Markdown

  

        
      

    


    

        



        

    

  


  

    

      
          
      

      
            changeset-bot
  Bot

      

      

      commented


        Jun 7, 2026



      
    


  





      


        



  
    

      
          
⚠️  No Changeset found


Latest commit: 81a7786


Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.


This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types




Click here to learn what changesets are, and how to add one.


Click here if you're a maintainer who wants to add a changeset to this PR


      		
    

  





        


            

            
            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    
















  
  

    

      

  










  








  
      

  
    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