Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 16, 2025

Updates the requirements on black, pytest and coverage to permit the latest version.
Updates black to 25.11.0

Release notes

Sourced from black's releases.

25.11.0

Highlights

  • Enable base 3.14 support (#4804)
  • Add support for the new Python 3.14 t-string syntax introduced by PEP 750 (#4805)

Stable style

  • Fix bug where comments between # fmt: off and # fmt: on were reformatted (#4811)
  • Comments containing fmt directives now preserve their exact formatting instead of being normalized (#4811)

Preview style

  • Move multiline_string_handling from --unstable to --preview (#4760)
  • Fix bug where module docstrings would be treated as normal strings if preceded by comments (#4764)
  • Fix bug where python 3.12 generics syntax split line happens weirdly (#4777)
  • Standardize type comments to form # type: <value> (#4645)
  • Fix fix_fmt_skip_in_one_liners preview feature to respect # fmt: skip for compound statements with semicolon-separated bodies (#4800)

Configuration

  • Add no_cache option to control caching behavior. (#4803)

Packaging

  • Releases now include arm64 Linux binaries (#4773)

Output

  • Write unchanged content to stdout when excluding formatting from stdin using pipes (#4610)

Blackd

  • Implemented BlackDClient. This simple python client allows to easily send formatting requests to blackd (#4774)

Integrations

  • Enable 3.14 base CI (#4804)
  • Enhance GitHub Action psf/black to support the required-version major-version-only "stability" format when using pyproject.toml (#4770)
  • Improve error message for vim plugin users. It now handles independently vim version
  • Vim: Warn on unsupported Vim and Python versions independently (#4772)
  • Vim: Print the import paths when importing black fails (#4675)
  • Vim: Fix handling of virtualenvs that have a different Python version (#4675)
Changelog

Sourced from black's changelog.

25.11.0

Highlights

  • Enable base 3.14 support (#4804)
  • Add support for the new Python 3.14 t-string syntax introduced by PEP 750 (#4805)

Stable style

  • Fix bug where comments between # fmt: off and # fmt: on were reformatted (#4811)
  • Comments containing fmt directives now preserve their exact formatting instead of being normalized (#4811)

Preview style

  • Move multiline_string_handling from --unstable to --preview (#4760)
  • Fix bug where module docstrings would be treated as normal strings if preceded by comments (#4764)
  • Fix bug where python 3.12 generics syntax split line happens weirdly (#4777)
  • Standardize type comments to form # type: <value> (#4645)
  • Fix fix_fmt_skip_in_one_liners preview feature to respect # fmt: skip for compound statements with semicolon-separated bodies (#4800)

Configuration

  • Add no_cache option to control caching behavior. (#4803)

Packaging

  • Releases now include arm64 Linux binaries (#4773)
  • Releases now include arm64 Windows binaries and wheels (#4814)

Output

  • Write unchanged content to stdout when excluding formatting from stdin using pipes (#4610)

Blackd

  • Implemented BlackDClient. This simple python client allows to easily send formatting requests to blackd (#4774)

Integrations

  • Enable 3.14 base CI (#4804)
  • Enhance GitHub Action psf/black to support the required-version major-version-only "stability" format when using pyproject.toml (#4770)
  • Improve error message for vim plugin users. It now handles independently vim version
  • Vim: Warn on unsupported Vim and Python versions independently (#4772)
  • Vim: Print the import paths when importing black fails (#4675)

... (truncated)

Commits

Updates pytest to 9.0.1

Release notes

Sourced from pytest's releases.

9.0.1

pytest 9.0.1 (2025-11-12)

Bug fixes

  • #13895: Restore support for skipping tests via raise unittest.SkipTest.
  • #13896: The terminal progress plugin added in pytest 9.0 is now automatically disabled when iTerm2 is detected, it generated desktop notifications instead of the desired functionality.
  • #13904: Fixed the TOML type of the verbosity settings in the API reference from number to string.
  • #13910: Fixed UserWarning: Do not expect file_or_dir on some earlier Python 3.12 and 3.13 point versions.

Packaging updates and notes for downstreams

  • #13933: The tox configuration has been adjusted to make sure the desired version string can be passed into its package_env through the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment variable as a part of the release process -- by webknjaz.

Contributor-facing changes

  • #13891, #13942: The CI/CD part of the release automation is now capable of creating GitHub Releases without having a Git checkout on disk -- by bluetech and webknjaz.
  • #13933: The tox configuration has been adjusted to make sure the desired version string can be passed into its package_env through the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment variable as a part of the release process -- by webknjaz.
Commits
  • d1b64aa Prepare release version 9.0.1
  • 0a497c7 regendoc: remove CI environment variables (#13950) (#13951)
  • a9f7e6e 🧪 Run gh release w/o Git in CI/CD (#13942) (#13947)
  • 2682a66 Merge pull request #13944 from pytest-dev/patchback/backports/9.0.x/bef7d34f1...
  • a999997 Merge pull request #13941 from nicoddemus/min-pre-commit-version
  • 4bd63a0 Merge pull request #13935 from pytest-dev/patchback/backports/9.0.x/ce8b8a7b4...
  • 15f93b3 Merge pull request #13933 from webknjaz/maintenance/tox-pep517-env-setuptools...
  • 0fa11ae Merge pull request #13927 from pytest-dev/patchback/backports/9.0.x/3d8075743...
  • fa45470 Merge pull request #13926 from pytest-dev/patchback/backports/9.0.x/d587e0cf8...
  • b4e3973 Merge pull request #13922 from bluetech/fix-argparse-userwarning
  • Additional commits viewable in compare view

Updates coverage to 7.11.3

Changelog

Sourced from coverage's changelog.

Version 7.11.3 — 2025-11-09

  • Fix: the 7.11.1 changes meant that conflicts between a requested measurement core and other settings would raise an error. This was a breaking change from previous behavior, as reported in issue 2076_ and issue 2078_.

    The previous behavior has been restored: when the requested core conflicts with other settings, another core is used instead, and a warning is issued.

  • For contributors: the repo has moved from Ned's nedbat GitHub account_ to the coveragepy GitHub organization_. The default branch has changed from master to main.

.. _issue 2076: coveragepy/coveragepy#2076 .. _issue 2078: coveragepy/coveragepy#2078 .. _nedbat GitHub account: https://github.com/nedbat .. _coveragepy GitHub organization: https://github.com/coveragepy

.. _changes_7-11-2:

Version 7.11.2 — 2025-11-08

  • Fix: using the "sysmon" measurement core in 7.11.1, if Python code was claimed to come from a non-Python file, a NotPython exception could be raised. This could happen for example with Jinja templates compiled to Python, as reported in issue 2077_. This is now fixed.

  • Doc: corrected the first entry in the 7.11.1 changelog.

.. _issue 2077: coveragepy/coveragepy#2077

.. _changes_7-11-1:

Version 7.11.1 — 2025-11-07

  • Fix: some chanages to details of how the measurement core is chosen, and how conflicting settings are handled. The "sysmon" core cannot be used with some conurrency settings, with dynamic context, and in Python 3.12/3.13, with branch measurement.

    • If the core is not specified and defaults to "sysmon" (Python 3.14+), but other settings conflict with sysmon, then the "ctrace" core will be used instead with no warning. For concurrency conflicts, this used to produce an error, as described in issue 2064_.

... (truncated)

Commits
  • 8bb1230 docs: remove duplicate entry in the changelog
  • 06c493c docs: sample HTML for 7.11.3
  • 0823a70 docs: prep for 7.11.3
  • 8434792 fix: sysmon conflicts no longer cause errors
  • 1f21184 chore: bump docker/setup-qemu-action in the action-dependencies group (#2080)
  • bd61620 docs: django_coverage_plugin moved
  • 1bd73f1 build: nedbat/coverage-reports moved to coveragepy/metacov-reports
  • b54131f docs: moved to coveragepy, master->main
  • f2d740f build: change more github urls to the coveragepy org
  • 776f313 docs: issue and pr references moved to coveragepy org
  • Additional commits viewable in compare view

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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

Updates the requirements on [black](https://github.com/psf/black), [pytest](https://github.com/pytest-dev/pytest) and [coverage](https://github.com/coveragepy/coveragepy) to permit the latest version.

Updates `black` to 25.11.0
- [Release notes](https://github.com/psf/black/releases)
- [Changelog](https://github.com/psf/black/blob/main/CHANGES.md)
- [Commits](psf/black@25.9.0...25.11.0)

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

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

---
updated-dependencies:
- dependency-name: black
  dependency-version: 25.11.0
  dependency-type: direct:development
  dependency-group: dev-deps
- dependency-name: pytest
  dependency-version: 9.0.1
  dependency-type: direct:development
  dependency-group: dev-deps
- dependency-name: coverage
  dependency-version: 7.11.3
  dependency-type: direct:development
  dependency-group: dev-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Nov 16, 2025
@zariiii9003 zariiii9003 merged commit 61a1e76 into main Nov 16, 2025
27 of 28 checks passed
@dependabot dependabot bot deleted the dependabot/pip/dev-deps-dc74908c26 branch November 16, 2025 11:36
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 Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants