Skip to content

chore(deps-dev): bump the uv-development group across 1 directory with 10 updates - #423

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/uv-development-d5d244fc69
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/uv-development-d5d244fc69

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the uv-development group with 10 updates in the / directory:

Package From To
mypy 2.4.0 2.4.1
pyrefly 1.3.2 1.4.1
basedpyright 1.40.1 1.40.2
pytest 9.1.1 9.2.0
hypothesis 6.168.3 6.170.15
poethepoet 0.48.0 0.49.0
pytest-asyncio 1.4.0 1.5.0
coverage 7.16.2 7.17.3
tox 4.64.7 4.67.13
mutmut 3.8.0 3.8.1

Updates mypy from 2.4.0 to 2.4.1

Changelog

Sourced from mypy's changelog.

Mypy 2.4.1

  • Process overloads as a whole in two-phase type checking (Ivan Levkivskyi, PR 22231)
  • Skip recursive setup for frame-private nested functions in mypyc (Piotr Sawicki, PR 22187)

Acknowledgements

Thanks to all mypy contributors who contributed to this release:

  • A5rocks
  • Adam Dangoor
  • Alex Waygood
  • Ali Hamdan
  • Brian Helba
  • Chad Dombrova
  • David Foster
  • dnwpark
  • Edgar Ramírez Mondragón
  • Giorgos Michas
  • Ivan Levkivskyi
  • Jelle Zijlstra
  • Jukka Lehtosalo
  • Marc Mueller
  • Michael R. Crusoe
  • NIYONSHUTI Emmanuel
  • Piotr Sawicki
  • Shantanu
  • themylogin
  • Vaggelis Danias
  • Willy Bruns

I'd also like to thank my employer, Dropbox, for supporting mypy development.

Mypy 2.3

We've just uploaded mypy 2.3.0 to the Python Package Index (PyPI). Mypy is a static type checker for Python. This release includes new features, performance improvements and bug fixes. You can install it as follows:

python3 -m pip install -U mypy

You can read the full documentation for this release on Read the Docs.

The Upcoming Switch to the New Native Parser

We are planning to enable the new native parser (--native-parser) by default soon. We recommend that you test the native parser in your projects and report any issues in the mypy issue tracker.

Mypyc Free-threading Memory Safety

... (truncated)

Commits

Updates pyrefly from 1.3.2 to 1.4.1

Release notes

Sourced from pyrefly's releases.

Pyrefly v1.4.1

Release date: November 4, 2026

Pyrefly v1.4.1 is a patch release that fixes bugs in pyrefly coverage. With these fixes, you can use pyrefly coverage check as a pre-commit hook (pyrefly-coverage-check in pyrefly-pre-commit).


🐛 Bug fixes

  • #5492: pyrefly coverage now gives the same result on every run. Before, an attribute that inherits its annotation from a base class in another module could be reported as typed on one run and untyped on the next.
  • #5362: pyrefly coverage report no longer panics when a pager or another program closes the output pipe early.
  • #5330: pyrefly coverage no longer reports an excluded function or class (for example, one decorated with @type_check_only or @no_type_check) as an untyped variable when a module-level loop follows it.
  • #5383: pyrefly coverage now counts a variable as typed when its value is an explicitly parameterized constructor call, such as x = set[int]().

✨ Improvements

  • #5329: pyrefly coverage understands Cython pure Python mode declarations in .py files.
  • pyrefly coverage skips the solver for annotations that are absent or already solved, which makes it faster on large projects.

Thank-you to all our contributors who found these bugs and reported them! Did you know this is one of the most helpful contributions you can make to an open-source project? If you find any bugs in Pyrefly we want to know about them! Please open a bug report issue here.


📦 Upgrade

pip install --upgrade pyrefly==1.4.1

How to safely upgrade your codebase

Upgrading the version of Pyrefly you're using or a third-party library you depend on can reveal new type errors in your code. Fixing them all at once is often unrealistic. We've written scripts to help you temporarily silence them. After upgrading, follow these steps:

  1. pyrefly check --suppress-errors
  2. Run your code formatter of choice
  3. pyrefly check --remove-unused-ignores
  4. Repeat until you achieve a clean formatting run and a clean type check.

This will add # pyrefly: ignore comments to your code, enabling you to silence errors and return to fix them later. This can make the process of upgrading a large codebase much more manageable.

Read more about error suppressions in the Pyrefly documentation.

Pyrefly v1.4.0

Release date: October 14, 2026

Pyrefly v1.4.0 bundles 1191 commits from 66 contributors.


Release Highlights

... (truncated)

Commits
  • b726cd5 cut 1.4.1
  • f87c157 release notes for v1.4.1 (pick onto fbcode/releases/pyrefly/v1.4)
  • 54fa035 Compare complete coverage slot counts directly in tests
  • 9bcd2fa Compact and encapsulate coverage annotation snapshots
  • 2577152 Avoid coverage solvers for absent or already solved annotations
  • af77a68 Share the pre-eviction coverage collector with regression tests
  • c6d6c2e Cover direct inherited annotations before and after eviction
  • 411fa40 Make inherited-annotated attributes deterministic in pyrefly coverage (#5492)
  • 0514db0 Add tests for coverage check and coverage --prefer-stubs (#4251)
  • 0b4cb4d Check the whole test corpus in the pyrefly coverage check/report consistenc...
  • Additional commits viewable in compare view

Updates basedpyright from 1.40.1 to 1.40.2

Release notes

Sourced from basedpyright's releases.

v1.40.2 (pyright 1.1.414)

What's Changed

Full Changelog: DetachHead/basedpyright@v1.40.1...v1.40.2

Commits
  • 3447596 asdf
  • 9c403f1 retry vscode publish because vs marketplace was down
  • fa4b52d 1.40.2
  • 3ca944f pin python version to 3.15
  • 1f4822c add python 3.15 builtin docstrings
  • 77cfb2d bump python dependencies & pnpm (#1877)
  • a8a92cd formatting
  • d55e86a Fix typeshed packaging for browser-basedpyright
  • c63390c delete dependabot config. too much of a pain in the ass to configure it to no...
  • 278e99c delete weekly typechecker benchmark workflow
  • Additional commits viewable in compare view

Updates pytest from 9.1.1 to 9.2.0

Release notes

Sourced from pytest's releases.

9.2.0

pytest 9.2.0 (2026-10-27)

Removals and backward incompatible breaking changes

  • #14716: -c now raises a usage error for a path that does not exist, is a directory, or is in a format pytest has no loader for. Such paths were previously either ignored or reported as an unhandled FileNotFoundError.

  • #8593: The indirect, ids and scope arguments of Metafunc.parametrize() <pytest.Metafunc.parametrize> -- and therefore of @pytest.mark.parametrize <pytest.mark.parametrize ref> -- are now keyword-only.

    Passing them positionally was a common source of confusing errors, e.g. parametrize("arg1", "arg2", [(1, 2)]) made the argvalues land in indirect and failed with indirect fixture '(1, 2)' doesn't exist; such mistakes now fail with an understandable TypeError. The type annotations have always declared these arguments as keyword-only.

  • #993: Plugin import failures at startup are now reported and classified instead of escaping as a raw traceback with the accidental exit code 1:

    • a plugin that cannot be found -- via -p, pytest_plugins or PYTEST_PLUGINS -- exits with pytest.ExitCode USAGE_ERROR (4), like a conftest.py that fails to import;
    • a plugin that is found but raises while importing -- including a broken pytest11 entry point or a missing plugin dependency -- exits with pytest.ExitCode INTERNAL_ERROR (3), with the traceback preserved.

    pytest.main now returns these codes instead of raising ImportError. Also fixed an IndexError from pytest's own internals when the plugin raised an exception with no arguments.

Deprecations (removal in next major release)

  • #14742: The private _pytest.python.CallSpec2 name has been renamed to CallSpec. The old CallSpec2 alias remains available for now and will be removed in pytest 10 or 11.

  • #14755: Schedule yield_fixture decorator for removal in pytest 10 or 11.

  • #14774: Similarly to the deprecation of class-scoped fixtures defined as instance methods in pytest 9.1, all higher-scoped fixtures (module, package, and session) defined as instance methods are now deprecated.

    They suffer from the same issue the original deprecation only fixed for class-scoped fixtures, see 10819 and 14011.

  • #14808: Passing a non-string value to a string-typed ini option now emits a pytest.PytestRemovedIn10Warning. This affects [tool.pytest.ini_options] in pyproject.toml. In pytest 10 this will raise a TypeError, matching the behavior of the corresponding TOML config path.

  • #7323: Passing bytes to TerminalReporter.write_line() is now deprecated, pass a str instead.

New features

  • #14743: Full diff: now contains a legend explaining the + & - symbols in diff output.
  • #2781: When strict_markers is enabled, marker names used in -m expressions are now validated against registered markers.
  • #6881: Added the parametrize_long_str_id_strategy configuration option to control how long str/bytes parameter values are handled in auto-generated test IDs. Explicit IDs set via ids=[...] or pytest.param(..., id=...) are not affected. Available strategies: short (default, values over 100 chars fall back to argname+index), sha256 (SHA-256 hex digest), legacy (keep full value), and disallow (error requesting explicit IDs).

Improvements in existing functionality

  • #10745: A RecursionError whose recursion origin cannot be located now shows only the first and last 10 stack frames, matching what pytest already did when locating the origin failed outright. Previously the full traceback -- often around a thousand near-identical frames -- was rendered, which was both slow and unreadable. Pass --full-trace to see every frame.

... (truncated)

Commits
  • ae1d0ff Prepare release version 9.2.0
  • 143ce31 pre-commit: exclude codespell on generated release announcements
  • 532dc5f tox: add attrs dependency to regen, needed in reportingdemo.rst
  • a7b2446 Merge pull request #15245 from pytest-dev/claude/project-thread-9jcf91
  • 679d09c [pre-commit.ci] pre-commit autoupdate (#15266)
  • 41d12cd docs: clarify typing for yield fixtures
  • b9022ba Merge pull request #15182 from 1871698/docs/improve-getting-started-description
  • 16f87a7 docs: improve getting-started.rst test execution description
  • 082ed70 Merge pull request #15255 from pytest-dev/claude/project-thread-eoi3d6
  • ae37a01 Merge pull request #15227 from pytest-dev/claude/project-thread-4etye4
  • Additional commits viewable in compare view

Updates hypothesis from 6.168.3 to 6.170.15

Commits
  • 9ab0be6 Bump hypothesis version to 6.170.15 and update changelog
  • 460d72f Merge pull request #4946 from jorenham/typing/errors/coverage
  • 26f1634 Enfore 100% public type coverage in CI with pyrefly coverage check
  • fb08018 version: fill in the missing type annotation
  • 7af7891 Rephrase release note as suggested in review
  • 95e0906 Add release notes
  • b7d5433 extra.ghostwriter: fill in the missing type annotations
  • 3537278 extra.codemods: fill in the missing type annotations
  • bd1a894 extra.dpcontracts: fill in the missing type annotation
  • 4bb761e errors: remove spurious blank line
  • Additional commits viewable in compare view

Updates poethepoet from 0.48.0 to 0.49.0

Release notes

Sourced from poethepoet's releases.

0.49.0

Enhancements

Fixes

  • Resolve glob patterns in cmd tasks after parameter expansion, so expansions and quotes inside square bracket patterns are respected and unmatched globs are passed on unescaped by @​nat-n in nat-n/poethepoet#425
  • Handle absolute glob patterns (e.g. /etc/host*) and ** within a path component in cmd tasks instead of crashing by @​nat-n in nat-n/poethepoet#431
  • Propagate errors and exit codes from failed subtasks: errors in a switch case or a ref'd task are no longer swallowed, and poe now exits with the exit code of the first failed subtask instead of 1 by @​nat-n in nat-n/poethepoet#430
  • Resolve subtask arg defaults against the env inherited from the parent task by @​nat-n in nat-n/poethepoet#421
  • Detect and report cyclic deps/uses instead of silently running nothing or crashing by @​nat-n in nat-n/poethepoet#421
  • Report malformed, empty, and non-table config files with clear errors instead of tracebacks by @​nat-n in nat-n/poethepoet#428
  • Fix boolean flags forwarded to python tasks being inverted when their default is templated by @​nat-n in nat-n/poethepoet#420

Breaking changes

These changes may affect a small number of existing configurations:

  • Consistent sys.argv for Python tasks with declared args. Script tasks that call a function, and expr tasks, now get the same sys.argv as script tasks that run a module: declared args as parsed (with defaults applied), followed by any args given after --. Templates like ${VAR} in args given on the command line are also no longer expanded for these tasks, matching other task types. See the migration guide for an example. (nat-n/poethepoet#420)

  • Square bracket glob patterns in cmd tasks are parsed like in bash. Whitespace, backslashes, quotes, and parameter expansions inside [...] are no longer taken literally, so e.g. [ -f foo ] is now four words rather than one pattern. To match a space or backslash, escape or quote it, e.g. [a\ b]. See the migration guide for details. (nat-n/poethepoet#425)

AI Agent Skill 🤖

  • Teach the task graph (deps, uses, uses_env) and steer agents towards declarative poe features rather than bash logic by @​nat-n in nat-n/poethepoet#429

Upgrade an installed skill with:

poe _install_skill --upgrade

New Contributors

Full Changelog: nat-n/poethepoet@v0.48.0...v0.49.0

Commits
  • b8e96a9 Bump version to 0.49.0
  • 98da6fe fix(cmd): handle absolute glob patterns and misplaced ** without crashing (...
  • 5e67f11 fix: propagate errors and exit codes from failed subtasks (#430)
  • 65f2390 fix!: resolve glob patterns in cmd tasks after parameter expansion (#425)
  • 0f56a81 docs(skill): teach the task graph and steer bash logic to poe features (#429)
  • eec9c33 fix!: consistent sys.argv for Python tasks with declared args (#420)
  • ac60c37 fix(config): report malformed and non-table config files cleanly (#428)
  • af160fe feat: support both .yaml and .yml file extensions (#426)
  • 31b931e fix: resolve subtask arg defaults against the inherited env, and detect cycli...
  • ee5b9bc feat: customize boolean argument string values (#419)
  • Additional commits viewable in compare view

Updates pytest-asyncio from 1.4.0 to 1.5.0

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio v1.5.0

1.5.0 - 2026-11-12

Added

  • A fixture-scope value for asyncio_default_fixture_loop_scope. With it, an asynchronous fixture without loop_scope uses its scope as its loop scope. This is the behavior of an unset option in pytest-asyncio 1.x. (#1095)

Fixed

  • Invalid arguments to the asyncio marker, including an invalid loop_scope, are reported with a message that names the test instead of a traceback. (#1584)

pytest-asyncio v1.4.1.post1

1.4.1.post1 - 2026-11-01

Changed

  • Removed the upper version bound on the pytest dependency. (#1605)

pytest-asyncio v1.4.1

1.4.1 - 2026-10-25

Added

  • Declared support for Python 3.15 (#1588)

Fixed

  • Allow AsyncIterable as a return type for asynchronous generator fixtures decorated with pytest_asyncio.fixture (#1090)

Notes for Downstream Packagers

  • Source-tree development dependencies now use PEP 735 dependency groups and uv.lock. (#1518)
Commits

Updates coverage from 7.16.2 to 7.17.3

Release notes

Sourced from coverage's releases.

7.17.3

Version 7.17.3 — 2026-11-11

  • Fix: using patch = fork, a child process wasn’t measured unless patch = subprocess was also used, as described in issue 2340. This is now fixed in pull 2342.
  • Fix: the JSON report keys functions and classes by name, but names can repeat, for example a property getter and setter. Only the last one was kept, so the others were missing from the report. Now repeated names get a @<line number> suffix, as in the LCOV report. pull 2353.
  • Fix: when combining parallel data files, a file that disappears after it has been listed (for example, when the process writing it is still finishing its write) is now reported with a warning, instead of stopping the combine with a DataError. This was a regression in 7.17.1. Closes issue 2364.
  • Fix: with patch = subprocess on Python 3.13, a measured subprocess that was stopped with SIGINT would exit with status 1 instead of dying from the signal. This was a regression in 7.17.1, and is now fixed, closing issue 2362.
  • Performance: on Python 3.13 and later, using the C tracer should result in test suites running about 8% to 12% faster (pull 2371).

➡️  PyPI page: coverage 7.17.3. :arrow_right:  To install: python3 -m pip install coverage==7.17.3

7.17.2

Version 7.17.2 — 2026-11-04

  • Fix: two different scenarios failed with “attempt to write a readonly database”. These were regressions in 7.17.1. They are fixed, closing issue 2356:
    • When using a version of SQLite older than 3.34.0, such as on RHEL 8 or Ubuntu 20.04, coverage combine (and pytest-cov, which combines automatically) always failed.
    • coverage combine and coverage debug data failed when a data file existed but had no coverage schema, for example an empty file left behind by a worker that died. A file we can’t read is now reported like any other unusable data file, and is left in place.

➡️  PyPI page: coverage 7.17.2. :arrow_right:  To install: python3 -m pip install coverage==7.17.2

7.17.1

Version 7.17.1 — 2026-11-03

  • Fix: a one-line class or function body immediately followed by another statement (such as class Foo: ... on its own line) was incorrectly reported as a missing branch when using the sys.monitoring core. This is now fixed, closing issue 2167 and issue 2337.
  • Fix: the HTML report only rewrites a file’s page when the file or its data has changed, but each page also links to the previous and next files. When the set of reported files changed, unchanged pages kept their old links. For example, with skip_covered, a file that became 100% covered had its page deleted, but the pages next to it still linked to it. Now a page is also rewritten when its neighbors change.
  • Fix: --fail-under now uses at least the decimal precision of the threshold for both the comparison and failure message. With precision=0, a total of 0.4 now passes --fail-under=0.3 and fails --fail-under=0.5 with the message “total of 0.4 is less than fail-under=0.5”. Previously, the comparison rounded the total to zero and the message could claim “1 is less than 0”. Closes issue 2295.
  • Fix: the HTML report escaped file names twice, so a name with &, <, or quotes in it was shown with entities like &amp;. Now they are properly escaped only once.
  • Fix: --source=/ measured no files. A file system root can’t be a source directory, so now it is an error. Closes issue 2291.
  • In an abundance of caution, prevent forged SQLite journal files from deleting files they shouldn’t.

➡️  PyPI page: coverage 7.17.1. :arrow_right:  To install: python3 -m pip install coverage==7.17.1

7.17.0

Version 7.17.0 — 2026-10-22

  • Dropped support for Python 3.10.
  • Binary wheels are now provided for iOS and Android. This allows the use of the optimized C tracer on mobile platforms.
  • Fix: three or more levels of nested with statements could make a with line look like a branch with an exit that can never happen. Using the sys.monitoring core, these phantom branches were reported as partial. Other cores hid the problem but still counted the phantom branches in the total. Closes issue 1987.
  • Fix: a comment or string that merely mentioned if True: or while True: could mark its line as a branch that is known to be partial, so a branch that never ran was reported as taken. These built-in patterns now only match at the start of the statement. Closes issue 2314.
  • Fix: region detection missed functions defined in unusual places, such as else and except clauses. This is now fixed.
  • Fix: recent versions of the lcov tool complain if the same function name appears more than once in a report. Python can have multiple same-named functions in a few ways, for example, getters/setters or conditionally defined functions. These are now disambiguated by adding a @<line number> suffix to the function name. Fixes issue 2335.
  • Fix: The “Can’t combine statement coverage data with branch data” error now names the two data files it couldn’t combine. The error description in the docs now lists common causes and how to find the process that wrote the file.
  • Fix: at coverage totals close to 0 or 100, the XML report could get incorrect line-rate values like 8.333e-05 or 1. This is now fixed, closing issue 2293 and issue 2294.
  • Fix: a parallel data file saved more than once kept the hash of its first save in its file name. Combining could then skip it as a duplicate of another file that had the same data at that point, and delete it, losing the data recorded after the first save. Each save now updates the hash. This had been a problem since 7.13.1. Fixes issue 2338.
  • Fixes for obscure but legal file names:
    • File names (and plugin names) can contain control characters, which are legal in POSIX paths but unsafe in reports: in XML 1.0 they make the document non-well-formed, and in a terminal they act as escape sequences (colors, title/clipboard sequences, cursor moves that forge output). Now the XML report, the text and Markdown summary reports, and coverage debug data replace non-printable characters in names. Printable names are unchanged.
    • A file pattern (from include, omit, or a [paths] alias) containing a newline sent the glob-to-regex translation into an infinite loop, hanging the process. Newlines in patterns are now handled like any other character.

... (truncated)

Changelog

Sourced from coverage's changelog.

Version 7.17.3 — 2026-11-11

  • Fix: using patch = fork, a child process wasn't measured unless patch = subprocess was also used, as described in issue 2340. This is now fixed in pull 2342.

  • Fix: the JSON report keys functions and classes by name, but names can repeat, for example a property getter and setter. Only the last one was kept, so the others were missing from the report. Now repeated names get a @<line number> suffix, as in the LCOV report. pull 2353_.

  • Fix: when combining parallel data files, a file that disappears after it has been listed (for example, when the process writing it is still finishing its write) is now reported with a warning, instead of stopping the combine with a DataError. This was a regression in 7.17.1. Closes issue 2364_.

  • Fix: with patch = subprocess on Python 3.13, a measured subprocess that was stopped with SIGINT would exit with status 1 instead of dying from the signal. This was a regression in 7.17.1, and is now fixed, closing issue 2362_.

  • Performance: on Python 3.13 and later, using the C tracer should result in test suites running about 8% to 12% faster (pull 2371_).

.. _issue 2340: coveragepy/coveragepy#2340 .. _pull 2342: coveragepy/coveragepy#2342 .. _pull 2353: coveragepy/coveragepy#2353 .. _issue 2364: coveragepy/coveragepy#2364 .. _issue 2362: coveragepy/coveragepy#2362 .. _pull 2371: coveragepy/coveragepy#2371

.. _changes_7-17-2:

Version 7.17.2 — 2026-11-04

  • Fix: two different scenarios failed with "attempt to write a readonly database". These were regressions in 7.17.1. They are fixed, closing issue 2356_:

    • When using a version of SQLite older than 3.34.0, such as on RHEL 8 or Ubuntu 20.04, coverage combine (and pytest-cov, which combines automatically) always failed.

    • coverage combine and coverage debug data failed when a data file existed but had no coverage schema, for example an empty file left behind by a worker that died. A file we can't read is now reported like any other

... (truncated)

Commits
  • e6580b2 build: use 24.04 for i686
  • c03b316 build: sample_html commits the updated sample
  • 07e6c88 docs: sample HTML for 7.17.3
  • 9bcfba6 docs: prep for 7.17.3
  • a1a76e6 docs: sample_html links will work once published
  • 00e7709 fix: keep the SIGINT exit status of a measured subprocess #2362
  • 89e8aef fix: report a vanishing parallel data file instead of crashing combine #2364 ...
  • 1cba103 refactor: use get_report() more
  • ca4c3bb refactor: use make_data_file() more
  • 96beedb refactor: use assert_file_count() more
  • Additional commits viewable in compare view

Updates tox from 4.64.7 to 4.67.13

Release notes

Sourced from tox's releases.

v4.67.13

Bug fixes

  • Relative {glob:...} and TOML replace = "glob" patterns now match files when tox_root contains [, * or ?. tox treats those characters in the project path literally while keeping wildcards in the configured pattern (#4389) by @​qodelicious and @​gaborbernat.
  • When work_dir or tox_root contains [, * or ?, tox now treats those characters literally in its own executable paths and in default or relative package_glob patterns. This lets it run environment commands and find packages built by package = external (#4390) by @​qodelicious and @​gaborbernat.

New Contributors

🐍 PyPI release

📜 Full Changelog

v4.67.12

Bug fixes

  • A quoted set_env value that ends with a literal backslash and contains a semicolon no longer loses its quote protection, so WINPATH="C:\tools;C:\bin\\" keeps the whole value instead of failing with invalid marker. tox now counts the backslashes in front of a quote: an even number leaves the quote unescaped (#4388) by @​haigou-web and @​gaborbernat. (#4387)

🐍 PyPI release

📜 Full Changelog

v4.67.11

Bug fixes

  • Package staging no longer fails on a .tox that only the project's own writers can change, such as one owned by the workspace owner while root runs tox, or a 777 build directory on Bitbucket. A work directory that other accounts could change, such as a 777 .tox left by an older tox under umask 000 or restored from a CI cache, is made private and emptied once at the start of a run, so tox recreates its environments instead of failing. When staging still refuses a path, the error names its owner and mode (#4386) by @​gaborbernat. (#4376)

🐍 PyPI release

📜 Full Changelog

v4.67.10

Bug fixes

  • A pair of numbers after a - is no longer read as a range, so py-django-4-2 keeps its name instead of splitting into py-django-4, 3 and 2. Braced ranges such as py-django-{4-5} still expand (#4380) by @​ericdelorefice and @​gaborbernat.
  • On Windows, quoted option values in requirements files and deps, such as -r "sub dir/base.txt", now have their quotes removed as they do on other platforms and in pip; before, the quotes stayed in the path and the file could not be opened. On every platform, a quoted -r, -c or -f value in deps keeps its spaces as written instead of gaining literal backslashes (#4381) by @​abo3losh1 and @​gaborbernat.

New Contributors

... (truncated)

Changelog

Sourced from tox's changelog.

########### Changelog ###########

.. towncrier-draft-entries:: Unreleased

.. towncrier release notes start

.. _release-4-67-15:


4.67.15 (2026-11-17)


.. _release-4-67-15-fixed:

Fixed

  • Create the work directory with owner-only access on POSIX also when no package is built; under a permissive umask it was created group-writable, leaving the environments inside it reachable by other accounts (:pr:4449) by :user:gaborbernat. (:issue:4444)

.. _release-4-67-14:


4.67.14 (2026-11-17)


.. _release-4-67-14-fixed:

Fixed

  • An environment name that combines an interpreter prefix with an explicit version, such as pypy-3.10, now works together with other factors. pypy-3.10-lint or tests-cpython-3.13 used to fail with conflicting factors, because the prefix and the version were read as two separate Python factors. With ignore_base_python_conflict, such an environment name now takes precedence over base_python as other Python factors already do, so pypy-3.10-lint runs on pypy3.10 instead of the configured base_python (:pr:4404) by :user:syahra712 and :user:gaborbernat.
  • A set_env entry with an empty name, such as =value in tox.ini or an environment file, or "" = "value" in a TOML table, now fails as invalid instead of passing an unnamed variable to the commands, which broke them on Windows (:pr:4423) by :user:arindam77 and :user:gaborbernat. (:issue:4422)
  • When tox writes set_env entries back out as lines, for example to combine a {[section]set_env} reference with an --override, a value ending in a backslash no longer swallows the environment marker that follows it, which made a variable scoped to one platform apply everywhere (:pr:4426) by :user:anwang132 and :user:gaborbernat. (:issue:4425)
  • An environment specific --override that appends with +=, such as testenv:py.deps+=pytest-xdist, now appends to the value the environment inherits from [testenv] or env_run_base instead of replacing it. Appending to a set such as labels adds to it, and appending to a single value such as description fails with

... (truncated)

Commits
  • fee635f release 4.67.13
  • b7f091f 🐛 fix(config): match relative globs in literal roots (#4389)
  • 4860d69 🐛 fix(env): handle glob characters in paths (#4390)
  • e06518d release 4.67.12
  • a6ce4cc 🐛 fix(set_env): keep quotes around a value ending with a backslash (#4388)
  • 11a2097 release 4.67.11
  • 514b084 🐛 fix(staging): trust project writers, rebuild exposed .tox (#4386)
  • e63f763 👷 ci: run release notes before PyPI publish (#4384)
  • be99e7f 👷 ci: reduce macOS runner use (#4385)
  • 9af3141 🧪 test(pylock): install from a local wheel (#4383)
  • Additional commits viewable in compare view

Updates mutmut from 3.8.0 to 3.8.1

Changelog

Sourced from mutmut's changelog.

3.8.1


* Fix stats collection crashing with pytest 9.2 (`[#615](https://github.com/boxed/mutmut/issues/615)`, `[#616](https://github.com/boxed/mutmut/issues/616)`)
  • Fix # pragma: no mutate being ignored inside multi-line statements ([#614](https://github.com/boxed/mutmut/issues/614))

  • Don't produce equivalent case mutants inside string escape sequences like   and \N{...} ([#609](https://github.com/boxed/mutmut/issues/609), [#611](https://github.com/boxed/mutmut/issues/611))

  • Fix enums with a custom __init__ failing to import under mutmut ([#600](https://github.com/boxed/mutmut/issues/600), [#603](https://github.com/boxed/mutmut/issues/603))

  • Fix crash when mutating float literals too large for a float, like 1e999 ([#604](https://github.com/boxed/mutmut/issues/604), [#605](https://github.com/boxed/mutmut/issues/605))

  • Fix crash when mypy reports no errors ([#598](https://github.com/boxed/mutmut/issues/598), [#599](https://github.com/boxed/mutmut/issues/599))

Commits
  • 41353df Release 3.8.1
  • e0bdba5 Fix stats collection crash with pytest 9.2 (#616)
  • c37062f Fix "pragma: no mutate" being ignored inside multi-line statements (#614)
  • 86564d8 Fix typo in README.rst (#612)
  • 09dc5dd Don't produce equivalent case mutants inside string escape sequences (#611)
  • 7d5fff3 Fix enums with custom __init__ failing to import under mutmut (#603)
  • 03beaf1 Fix crash when mutating float literals too large for a float (

@dependabot
dependabot Bot requested a review from a team as a code owner November 4, 2026 00:27
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code labels Nov 4, 2026
@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

AI review: 1 P0-P2 finding(s)

Reviewed 977e4d8. Run log

Dependabot bumps ten pinned dev tools (pyrefly, basedpyright, pytest, hypothesis, poethepoet, pytest-asyncio, coverage, tox, mutmut, plus mypy in the lock only) and regenerates uv.lock, which also moves it to revision = 5 and drops the now-unused pastel package. Runtime risk is low. The earlier P1 still applies at this head: the basedpyright pin in the tox package-types env changed, but the quality-policy lock wasn't updated, so the policy step of poe checks will fail.

🟠 P1

  • pyproject.toml:340 basedpyright tox pin bumped without updating the quality-policy lock, so poe policy fails (also reported as: The basedpyright Tox pin no longer matches the policy snapshot)

Not checked: The AI review read the diff, the code, and the PR's text; it ran no tests or builds and read nothing outside this repository.

  • Whether uv 0.12.17, the version CI pins, accepts the lockfile's new revision = 5 under uv sync --locked/uv run --locked.
  • Whether the suite still passes under pytest 9.2.0 and pytest-asyncio 1.5.0 with filterwarnings = ["error"] and strict = true.
  • Whether coverage 7.17.x branch-analysis changes keep the 100% fail_under threshold in the Python 3.12.14 coverage run.
  • Whether pyrefly 1.4.1 reports new errors in mutmut's type_check_command and so changes which mutants count as type-checked.
  • Verify that CI's pinned uv 0.12.17 accepts uv.lock revision 5 under uv sync --locked.

Push a fix, or have a collaborator with write access (including the PR author) add the ai-review-override label to accept 977e4d8 as is. An override also needs a human review.

Failing round 1 of 3 since this PR was last marked ready for review. If 3 rounds in a row find P0-P2 problems, the AI review moves the PR back to draft for the author to re-assess the approach.

Human review: not needed

Comment thread pyproject.toml
[tool.tox.env.package-types]
extras = ["durable"]
deps = ["basedpyright==1.40.1"]
deps = ["basedpyright==1.40.2"]

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 P1: basedpyright tox pin bumped without updating the quality-policy lock, so poe policy fails

[tool.tox.env.package-types].deps changes to basedpyright==1.40.2, but maintainers/quality-policy.lock.json (line 324) still records basedpyright==1.40.1. scripts/check_quality_policy.py:check_config requires the whole [tool] table to match the lock exactly. It will report tool.tox.env.package-types.deps and exit 1. policy is the first step of poe checks, which CI runs in all four test jobs, so every job fails and Quality Gate blocks the merge. maintainers/releasing.md says this explicitly: "The ruff, hatchling and basedpyright pins are also recorded in the policy lock, so update the lock and its digest with them." Fix: change the lock entry to basedpyright==1.40.2 and update LOCK_SHA256 in scripts/check_quality_policy.py to the new file's SHA-256. Dependabot stops rebasing once someone else pushes, so merge soon after.

Found by claude-opus-5-5

Comment thread pyproject.toml
[tool.tox.env.package-types]
extras = ["durable"]
deps = ["basedpyright==1.40.1"]
deps = ["basedpyright==1.40.2"]

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 P1: Update the policy snapshot alongside the Tox pin

maintainers/quality-policy.lock.json still records basedpyright==1.40.1 for this environment. Because scripts/check_quality_policy.py::check_config compares the entire tool configuration against that snapshot, uv run --locked poe checks in .github/workflows/ci.yml fails at the policy task on every Python matrix entry. Update the snapshot and its LOCK_SHA256 digest in the policy checker alongside this pin.

Found by gpt-6.1-sol

…h 10 updates

Bumps the uv-development group with 10 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [mypy](https://github.com/python/mypy) | `2.4.0` | `2.4.1` |
| [pyrefly](https://github.com/facebook/pyrefly) | `1.3.2` | `1.4.1` |
| [basedpyright](https://github.com/detachhead/basedpyright) | `1.40.1` | `1.40.2` |
| [pytest](https://github.com/pytest-dev/pytest) | `9.1.1` | `9.2.0` |
| [hypothesis](https://github.com/HypothesisWorks/hypothesis) | `6.168.3` | `6.170.15` |
| [poethepoet](https://github.com/nat-n/poethepoet) | `0.48.0` | `0.49.0` |
| [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) | `1.4.0` | `1.5.0` |
| [coverage](https://github.com/coveragepy/coveragepy) | `7.16.2` | `7.17.3` |
| [tox](https://github.com/tox-dev/tox) | `4.64.7` | `4.67.13` |
| [mutmut](https://github.com/boxed/mutmut) | `3.8.0` | `3.8.1` |



Updates `mypy` from 2.4.0 to 2.4.1
- [Changelog](https://github.com/python/mypy/blob/master/CHANGELOG.md)
- [Commits](python/mypy@v2.4.0...v2.4.1)

Updates `pyrefly` from 1.3.2 to 1.4.1
- [Release notes](https://github.com/facebook/pyrefly/releases)
- [Commits](pyrefly-org/pyrefly@1.3.2...1.4.1)

Updates `basedpyright` from 1.40.1 to 1.40.2
- [Release notes](https://github.com/detachhead/basedpyright/releases)
- [Commits](DetachHead/basedpyright@v1.40.1...v1.40.2)

Updates `pytest` from 9.1.1 to 9.2.0
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@9.1.1...9.2.0)

Updates `hypothesis` from 6.168.3 to 6.170.15
- [Release notes](https://github.com/HypothesisWorks/hypothesis/releases)
- [Commits](HypothesisWorks/hypothesis@v6.168.3...v6.170.15)

Updates `poethepoet` from 0.48.0 to 0.49.0
- [Release notes](https://github.com/nat-n/poethepoet/releases)
- [Commits](nat-n/poethepoet@v0.48.0...v0.49.0)

Updates `pytest-asyncio` from 1.4.0 to 1.5.0
- [Release notes](https://github.com/pytest-dev/pytest-asyncio/releases)
- [Commits](pytest-dev/pytest-asyncio@v1.4.0...v1.5.0)

Updates `coverage` from 7.16.2 to 7.17.3
- [Release notes](https://github.com/coveragepy/coveragepy/releases)
- [Changelog](https://github.com/coveragepy/coveragepy/blob/main/CHANGES.rst)
- [Commits](coveragepy/coveragepy@7.16.2...7.17.3)

Updates `tox` from 4.64.7 to 4.67.13
- [Release notes](https://github.com/tox-dev/tox/releases)
- [Changelog](https://github.com/tox-dev/tox/blob/main/docs/changelog.rst)
- [Commits](tox-dev/tox@4.64.7...4.67.13)

Updates `mutmut` from 3.8.0 to 3.8.1
- [Release notes](https://github.com/boxed/mutmut/releases)
- [Changelog](https://github.com/boxed/mutmut/blob/main/HISTORY.rst)
- [Commits](boxed/mutmut@3.8.0...3.8.1)

---
updated-dependencies:
- dependency-name: basedpyright
  dependency-version: 1.40.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: uv-development
- dependency-name: coverage
  dependency-version: 7.17.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: uv-development
- dependency-name: hypothesis
  dependency-version: 6.170.13
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: uv-development
- dependency-name: mutmut
  dependency-version: 3.8.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: uv-development
- dependency-name: mypy
  dependency-version: 2.4.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: uv-development
- dependency-name: poethepoet
  dependency-version: 0.49.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: uv-development
- dependency-name: pyrefly
  dependency-version: 1.4.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: uv-development
- dependency-name: pytest
  dependency-version: 9.2.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: uv-development
- dependency-name: pytest-asyncio
  dependency-version: 1.4.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: uv-development
- dependency-name: tox
  dependency-version: 4.67.4
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: uv-development
...

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

dependabot Bot commented on behalf of github Nov 18, 2026

Copy link
Copy Markdown
Contributor Author

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

@dependabot dependabot Bot closed this Nov 18, 2026
@dependabot
dependabot Bot deleted the dependabot/uv/uv-development-d5d244fc69 branch November 18, 2026 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants