Skip to content

⬆ Bump the dev-dependencies group across 1 directory with 4 updates - #229

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/dev-dependencies-fce62d09da
Closed

⬆ Bump the dev-dependencies group across 1 directory with 4 updates#229
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/dev-dependencies-fce62d09da

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 2, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Updates the requirements on pre-commit, ruff, vcrpy and uv-build to permit the latest version.
Updates pre-commit from 4.6.0 to 4.6.1

Release notes

Sourced from pre-commit's releases.

pre-commit v4.6.1

Fixes

Changelog

Sourced from pre-commit's changelog.

4.6.1 - 2026-07-21

Fixes

Commits
  • 242ce8a v4.6.1
  • 766e550 Merge pull request #3727 from pre-commit/dedupe
  • 1558d06 Merge pull request #3726 from pre-commit/exists-faster
  • 8a1c47a avoid duplicate files in --all-files during conflict
  • 2e01c99 faster check of rev existing locally as a commit
  • 3613bf2 Merge pull request #3701 from pre-commit/autoupdate-repos
  • 1d811d9 Return an error for invalid --repo
  • 374d354 Merge pull request #3711 from damonbayer/dmb_JULIA_DEPOT_PATH
  • 1e7994f set JULIA_DEPOT_PATH
  • b2b9119 Merge pull request #3719 from pre-commit/npm-unknown-options
  • Additional commits viewable in compare view

Updates ruff from 0.15.18 to 0.16.0

Release notes

Sourced from ruff's releases.

0.16.0

Release Notes

Released on 2026-07-23.

Check out the blog post for a migration guide and overview of the changes!

Breaking changes

  • Ruff now enables a much larger set of rules by default (413, up from 59). See the blog post for more details and the new Default Rules page for a full listing of the enabled rules. Note that this is primarily an expansion, but 18 of the more opinionated pycodestyle (E) and pyflakes (F) rules have been removed from the default set: E401, E402, E701, E702, E703, E711, E712, E713, E714, E721, E731, E741, E742, E743, F403, F405, F406, and F722.

  • Ruff can now format Python code blocks in Markdown files and will do this by default. See the documentation for more details.

  • Ruff now supports ruff: ignore comments at the ends of lines, like noqa comments, or on the line preceding a diagnostic. For example, these both suppress an unused-import (F401) diagnostic:

    import math  # ruff: ignore[F401]
ruff: ignore[F401]
import os

  • Fixes are now shown in check and format --check output:

    ❯ ruff format --check .
unformatted: File would be reformatted
 --> try.md:1:1
  |
1 | ```python
  - import   math
2 + import math
3 | ```
  |
1 file would be reformatted

    This example also shows off the Markdown formatting.

  • format --check now supports the same output formats as the linter, including the github and gitlab outputs for rendering annotations in CI:

    ❯ ruff format --check --output-format github .
::error title=ruff (unformatted),file=try.md,line=2,col=8,endLine=2,endColumn=10::try.md:2:8: unformatted: File would be reformatted

    See the CLI help or documentation for the full list of supported formats.

  • The filename, location, end_location, fix.edits[].location, and fix.edits[].end_location fields in the JSON output format may now be null rather than defaulting to the empty string and row 1, column 1, respectively.

... (truncated)

Changelog

Sourced from ruff's changelog.

0.16.0

Released on 2026-07-23.

Check out the blog post for a migration guide and overview of the changes!

Breaking changes

  • Ruff now enables a much larger set of rules by default (413, up from 59). See the blog post for more details and the new Default Rules page for a full listing of the enabled rules. Note that this is primarily an expansion, but 18 of the more opinionated pycodestyle (E) and pyflakes (F) rules have been removed from the default set: E401, E402, E701, E702, E703, E711, E712, E713, E714, E721, E731, E741, E742, E743, F403, F405, F406, and F722.

  • Ruff can now format Python code blocks in Markdown files and will do this by default. See the documentation for more details.

  • Ruff now supports ruff: ignore comments at the ends of lines, like noqa comments, or on the line preceding a diagnostic. For example, these both suppress an unused-import (F401) diagnostic:

    import math  # ruff: ignore[F401]
ruff: ignore[F401]
import os

  • Fixes are now shown in check and format --check output:

    ❯ ruff format --check .
unformatted: File would be reformatted
 --> try.md:1:1
  |
1 | ```python
  - import   math
2 + import math
3 | ```
  |
1 file would be reformatted

    This example also shows off the Markdown formatting.

  • format --check now supports the same output formats as the linter, including the github and gitlab outputs for rendering annotations in CI:

    

    • 






... (truncated)





Commits

    

  • a2635fd Bump 0.16.0 (#27136)
    • 

  • 3433449 [ty] Reuse full call diagnostics for implicit setter calls (#27115)
    • 

  • 2240070 Reflect ruff: ignore and --add-ignore stabilization in documentation (#27...
    • 

  • 17ef711 Stabilize --add-ignore (#27125)
    • 

  • ef912bb Add newly stabilized rules to defaults (#27055)
    • 

  • b30f040 Stabilize new default rules (#27035)
    • 

  • bcd70c5 Exclude Markdown files from format-dev runs (#27052)
    • 

  • 87e51e2 Fix format --check spans for syntax errors (#27045)
    • 

  • afe2723 [flake8-gettext] Stabilize qualified-name and built-in binding resolution (...
    • 

  • a9702d8 [flake8-bandit] Stabilize string literal binding resolution (S310) (#26944)
    • 

  • Additional commits viewable in compare view
    • 







Updates vcrpy from 8.2.1 to 8.3.0



Release notes

Sourced from vcrpy's releases.




v8.3.0


What's Changed


    

  • Add support for niquests (#980) — thanks @​ionelmc
    • 

  • Recording now fails fast if a request or response contains a Python object the safe YAML loader (introduced in 8.2.1) couldn't read back, instead of writing a cassette that breaks on replay. The error shows exactly how to register the object if you need it (#1007, #1009) — thanks @​Polandia94
    • 

  • New vcr.serializers.yamlserializer.with_custom_tags(...) builds a YAML serializer supporting custom Python object tags on both record and replay, registered per VCR instance via register_serializer (#1007, #1009) — thanks @​Polandia94
    • 

  • Clearer error when a cassette contains an unsupported YAML tag, and the stale git.io migration link is gone (#1007, #1008) — thanks @​gaoflow
    • 

  • Fix stale keep-alive connection reuse across cassettes; unpin werkzeug (#1001)
    • 



Full Changelog: kevin1024/vcrpy@v8.2.1...v8.3.0







Changelog

Sourced from vcrpy's changelog.




Changelog


All help in providing PRs to close out bug issues is appreciated. Even if that is providing a repo that fully replicates issues. We have very generous contributors that have added these to bug issues which meant another contributor picked up the bug and closed it out.


    

  • 

    8.3.0
    

      

    • Add support for niquests (#980) - thanks @​ionelmc
      • 

    • Refuse to record a cassette containing a Python object the safe YAML loader could not read back, so recording fails fast instead of producing a cassette that breaks on replay (#1007, #1009) - thanks @​Polandia94
      • 

    • Add vcr.serializers.yamlserializer.with_custom_tags to build a YAML serializer supporting custom Python object tags on both record and replay, registered per VCR instance via register_serializer (#1007, #1009) - thanks @​Polandia94
      • 

    • Clearer error when a cassette contains an unsupported YAML tag, and remove the stale git.io migration link (#1007, #1008) - thanks @​gaoflow
      • 

    • Fix stale keep-alive connection reuse across cassettes; unpin werkzeug (#1001)
      • 

    

    • 

  • 

    8.2.1
    

      

    • SECURITY: Load cassettes with a safe YAML loader, preventing arbitrary code execution when a cassette from an untrusted source is loaded (GHSA-rpj2-4hq8-938g) - thanks @​RamiAltai and @​EQSTLab
      • 

    • Validate record_mode and raise a clear error on an invalid value (#208)
      • 

    • Recommend pytest-recording over the unmaintained pytest-vcr in the docs (#986)
      • 

    

    • 

  • 

    8.2.0
    

      

    • Add support for httpx 2.x (#993) - thanks @​dsfaccini
      • 

    • Patch httpx transports instead of httpcore (#972) - thanks @​seowalex
      • 

    • Fix aiohttp 3.14 compatibility: AsyncStreamReaderMixin removed and ClientResponse now requires stream_writer (#995) - thanks @​dsfaccini
      • 

    • Account for modified requests when storing played cassettes, so drop_unused_requests honours before_record_request filtering (#962) - thanks @​jamesbraza
      • 

    • Make the request URL available on VCRHTTPResponse (#976) - thanks @​dAnjou
      • 

    • Improve error message when a matching request has already been consumed (#985) - thanks @​Polandia94
      • 

    • Fix body check in convert_body_to_unicode to use an explicit type check (#982) - thanks @​Polandia94
      • 

    • Add env proxy cassette regression test (#994) - thanks @​tine1117
      • 

    • Remove milestone references from docs (#984) - thanks @​Polandia94
      • 

    • CI: bump sphinx-rtd-theme from 3.0.2 to 3.1.0 (#973)
      • 

    

    • 

  • 

    8.1.1
    

      

    • Fix sync requests in async contexts for HTTPX (#965) - thanks @​seowalex
      • 

    • CI: bump peter-evans/create-pull-request from 7 to 8 (#969)
      • 

    

    • 

  • 

    8.1.0
    


    • 

  • 

    8.0.0
    

      

    • BREAKING: Drop support for Python 3.9 (major version bump) - thanks @​jairhenrique
      • 

    • BREAKING: Drop support for urllib3 < 2 - fixes CVE warnings from urllib3 1.x (#926, #880) - thanks @​jairhenrique
      • 

    • New feature: drop_unused_requests option to remove unused interactions from cassettes (#763) - thanks @​danielnsilva
      • 

    • Rewrite httpx support to patch httpcore instead of httpx (#943) - thanks @​seowalex

        

      • Fixes httpx.ResponseNotRead exceptions (#832, #834)
        • 

      • Fixes KeyError: 'follow_redirects' (#945)
        • 

      • Adds support for custom httpx transports
        • 

      

      • 

    • Fix HTTPS proxy handling - proxy address no longer ends up in cassette URIs (#809, #914) - thanks @​alga
      • 

    

    • 






... (truncated)





Commits






Updates uv-build to 0.12.0



Release notes

Sourced from uv-build's releases.




0.12.0


Release Notes


Released on 2026-07-28.


Since we released uv 0.11.0 in March, we've accumulated changes that improve correctness, safety, and compatibility with specifications, but could break some workflows. This release contains those changes; many have been marked as breaking out of an abundance of caution.


We expect most users to be able to upgrade without making changes.


There are no breaking changes to the configuration of the uv build backend. If your [build-system] table includes an upper bound on uv_build, update it to allow uv_build 0.12, e.g., uv_build>=0.11.32,<0.13.


Breaking changes


    

  • 

    Define build systems by default with uv init (#19197)
    

    Projects created with uv init now declare a build system and are packaged by default. This was the default project layout all the way back in v0.3, but we found that the use of the hatchling build system was confusing to newcomers and consequently dropped use of a build system by default in v0.4. Since then, we've created our own build system (uv_build) with tight integration with uv and are excited to restore the default to a best-practice project layout.
    

    Previously, uv init example created an unpackaged layout containing main.py and a pyproject.toml without a build system. The project could declare dependencies but was not itself installed into its virtual environment.
    

    Now, uv init example defines a [build-system] using uv_build, places application source code in src/example, and includes a [project.scripts] entry named example. Defining a build system allows the project to be imported from tests or other code, installed as a dependency, and run as a command:
    

    $ uv init example
$ cd example
$ uv run example
Hello from example!
    

    Existing projects are unaffected. Use uv init --no-package example to create the previous unpackaged layout without a build system.
    

    See the project creation documentation for more details.
    

    This stabilizes the packaged-init preview feature.
    

    • 

  • 

    Reject unsupported source distribution and wheel archive formats (#18927)
    

    PEP 625 requires source distributions to use .tar.gz archives. Previously, uv also accepted legacy formats such as .tar.bz2 and .tar.xz. Those formats are now rejected, including when referenced by an existing lockfile. Legacy .zip source distributions remain supported for backwards compatibility.
    

    Wheels and other ZIP archives can no longer contain entries compressed with bzip2, LZMA, or XZ. Entries must use the stored, DEFLATE, or zstd compression methods.
    

    Removing support for uncommon compression methods reduces uv's compression dependencies and the attack surface exposed when processing untrusted packages.
    

    You cannot opt out of this behavior. If you depend on a legacy source distribution that uses an unsupported format, we recommend rebuilding it as a .tar.gz archive and regenerating any lockfile containing references to the legacy archive.
    

    • 

  • 

    Reject wheel files that could replace the Python interpreter (#20748, #20749)
    

    uv already rejected wheel entry points named python, but case variants such as Python were still accepted. On case-insensitive filesystems, including common macOS and Windows setups, these entry points could overwrite the virtual environment's interpreter.
    

    Wheels could also place interpreter files in their .data/scripts directory or in paths such as .data/data/bin/python, bypassing the entry-point check and replacing the interpreter during installation.
    

    • 






... (truncated)





Changelog

Sourced from uv-build's changelog.




0.12.0


Released on 2026-07-28.


Since we released uv 0.11.0 in March, we've accumulated changes that improve correctness, safety, and compatibility with specifications, but could break some workflows. This release contains those changes; many have been marked as breaking out of an abundance of caution.


We expect most users to be able to upgrade without making changes.


There are no breaking changes to the configuration of the uv build backend. If your [build-system] table includes an upper bound on uv_build, update it to allow uv_build 0.12, e.g., uv_build>=0.11.32,<0.13.


Breaking changes


    

  • 

    Define build systems by default with uv init (#19197)
    

    Projects created with uv init now declare a build system and are packaged by default. This was the default project layout all the way back in v0.3, but we found that the use of the hatchling build system was confusing to newcomers and consequently dropped use of a build system by default in v0.4. Since then, we've created our own build system (uv_build) with tight integration with uv and are excited to restore the default to a best-practice project layout.
    

    Previously, uv init example created an unpackaged layout containing main.py and a pyproject.toml without a build system. The project could declare dependencies but was not itself installed into its virtual environment.
    

    Now, uv init example defines a [build-system] using uv_build, places application source code in src/example, and includes a [project.scripts] entry named example. Defining a build system allows the project to be imported from tests or other code, installed as a dependency, and run as a command:
    

    $ uv init example
$ cd example
$ uv run example
Hello from example!
    

    Existing projects are unaffected. Use uv init --no-package example to create the previous unpackaged layout without a build system.
    

    See the project creation documentation for more details.
    

    This stabilizes the packaged-init preview feature.
    

    • 

  • 

    Reject unsupported source distribution and wheel archive formats (#18927)
    

    PEP 625 requires source distributions to use .tar.gz archives. Previously, uv also accepted legacy formats such as .tar.bz2 and .tar.xz. Those formats are now rejected, including when referenced by an existing lockfile. Legacy .zip source distributions remain supported for backwards compatibility.
    

    Wheels and other ZIP archives can no longer contain entries compressed with bzip2, LZMA, or XZ. Entries must use the stored, DEFLATE, or zstd compression methods.
    

    Removing support for uncommon compression methods reduces uv's compression dependencies and the attack surface exposed when processing untrusted packages.
    

    You cannot opt out of this behavior. If you depend on a legacy source distribution that uses an unsupported format, we recommend rebuilding it as a .tar.gz archive and regenerating any lockfile containing references to the legacy archive.
    

    • 

  • 

    Reject wheel files that could replace the Python interpreter (#20748, #20749)
    

    uv already rejected wheel entry points named python, but case variants such as Python were still accepted. On case-insensitive filesystems, including common macOS and Windows setups, these entry points could overwrite the virtual environment's interpreter.
    

    Wheels could also place interpreter files in their .data/scripts directory or in paths such as .data/data/bin/python, bypassing the entry-point check and replacing the interpreter during installation.
    

    uv now rejects case-insensitive variants of reserved interpreter names and wheel data files that would be installed over an interpreter. This includes names such as Python, python.py, and Python.exe, along with other reserved interpreter names and their versioned variants.
    

    You cannot opt out of these checks. Rename conflicting entry points or wheel data files and rebuild the affected wheel.
    

    • 






... (truncated)





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 stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
    • 

  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
    • 

  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    • 




    

  
  



      


          

          
  
  

    
  
    
    

  

  

  



                    

          
        





  





    



      

  
        

  

      

  
  

  
          

  

    

      


  

        
          @dependabot
  




      

        
          ⬆ Bump the dev-dependencies group across 1 directory with 4 updates
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          aee4269
        
      

    

  

    

      
Updates the requirements on [pre-commit](https://github.com/pre-commit/pre-commit), [ruff](https://github.com/astral-sh/ruff), [vcrpy](https://github.com/kevin1024/vcrpy) and [uv-build](https://github.com/astral-sh/uv) to permit the latest version.

Updates `pre-commit` from 4.6.0 to 4.6.1
- [Release notes](https://github.com/pre-commit/pre-commit/releases)
- [Changelog](https://github.com/pre-commit/pre-commit/blob/main/CHANGELOG.md)
- [Commits](pre-commit/pre-commit@v4.6.0...v4.6.1)

Updates `ruff` from 0.15.18 to 0.16.0
- [Release notes](https://github.com/astral-sh/ruff/releases)
- [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md)
- [Commits](astral-sh/ruff@0.15.18...0.16.0)

Updates `vcrpy` from 8.2.1 to 8.3.0
- [Release notes](https://github.com/kevin1024/vcrpy/releases)
- [Changelog](https://github.com/kevin1024/vcrpy/blob/master/docs/changelog.rst)
- [Commits](kevin1024/vcrpy@v8.2.1...v8.3.0)

Updates `uv-build` to 0.12.0
- [Release notes](https://github.com/astral-sh/uv/releases)
- [Changelog](https://github.com/astral-sh/uv/blob/main/CHANGELOG.md)
- [Commits](astral-sh/uv@0.11.23...0.12.0)

---
updated-dependencies:
- dependency-name: pre-commit
  dependency-version: 4.6.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: ruff
  dependency-version: 0.16.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: vcrpy
  dependency-version: 8.3.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: uv-build
  dependency-version: 0.12.0
  dependency-type: direct:development
  dependency-group: dev-dependencies
...

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

    







  








      

  
            

    

      
    

    


      


          @dependabot
dependabot
Bot



            added
      

  dependencies

  Pull requests that update a dependency file

      

  python:uv

  Pull requests that update python:uv code

  labels


      Aug 2, 2026

    

  








      

  
      



  

  @dependabot


    @github




  



    

      

  

    

      
          
      

      
            dependabot
    Bot

      

      

      commented

        on behalf of github

        Aug 2, 2026



      
    


  


  

    

      

          
    
    

  


        
            
  
      
              Copy link

  

            
  
      
              Copy Markdown

  

        
      

    


    

        

  
    Contributor


        

  Author


    

  





      


        



  
    

      
          
Looks like these dependencies are updatable in another way, so this is no longer needed.


      		
    

  





        

            

            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    












      

  
            

    

      
    

    


      


          @dependabot
dependabot
Bot



          closed this


      Aug 2, 2026

    

  


    


  

  
  

  
    

        

              @dependabot


        

      

            dependabot
Bot

        
    deleted the
    
      
        dependabot/uv/dev-dependencies-fce62d09da
    
    branch

        August 2, 2026 20:44        
        
      

    














  
  

    

      

  










  








  
      

  
    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
  

    python:uv

  Pull requests that update python:uv code








      

  

    

        

    Projects
  


        




    None yet




  



      


  

    
  

    Milestone
  


      No milestone





    
      
          


  

    

      
        

          
  

    Development
  



            


Successfully merging this pull request may close these issues.





  
  



      
    

  




      

    

  
        

  

    

      0 participants