chore(deps): bump the production-dependencies group with 4 updates #76

dependabot · 2025-11-10T10:06:03Z

Bumps the production-dependencies group with 4 updates: coverage, pre-commit, pytest and python-semantic-release.

Updates coverage from 7.11.0 to 7.11.3

Release notes

7.11.3

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.

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

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.

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

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.

If the “sysmon” core is explicitly requested in your configuration, but other settings conflict, an error is now raised. This used to produce a warning.

Fix: some multi-line case clauses or for loops (and probably other constructs) could cause incorrect claims of missing branches with the sys.monitoring core, as described in issue 2070. This is now fixed.

Fix: when running in pytest under coverage, a breakpoint() would stop in the wrong frame, one level down from where it should, as described in issue 1420. This was due to a coverage change in v6.4.1 that seemed to give a slight performance improvement, but I couldn’t reproduce the performance gain, so it’s been reverted, fixing the debugger problem.

A new debug option --debug=core shows which core is in use and why.

Split sqlite debugging information out of the sys coverage debug and --debug option options since it’s bulky and not very useful.

Updated the How coverage.py works page to better describe the three different measurement cores.

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

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.

If the “sysmon” core is explicitly requested in your configuration, but other settings conflict, an error is now raised. This used to produce a warning.

Fix: some multi-line case clauses or for loops (and probably other constructs) could cause incorrect claims of missing branches with the sys.monitoring core, as described in issue 2070. This is now fixed.

Fix: when running in pytest under coverage, a breakpoint() would stop in the wrong frame, one level down from where it should, as described in issue 1420. This was due to a coverage change in v6.4.1 that seemed to give a slight performance improvement, but I couldn’t reproduce the performance gain, so it’s been reverted, fixing the debugger problem.

A new debug option --debug=core shows which core is in use and why.

Split sqlite debugging information out of the sys coverage debug and --debug option options since it’s bulky and not very useful.

Updated the How coverage.py works page to better describe the three different measurement cores.

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

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

Updates pre-commit from 4.3.0 to 4.4.0

Release notes

Sourced from pre-commit's releases.

pre-commit v4.4.0

Features

Add --fail-fast option to pre-commit run.

#3528 PR by @JulianMaurin.

Upgrade ruby-build / rbenv.

#3566 PR by @asottile.

#3565 issue by @MRigal.

Add language: unsupported / language: unsupported_script as aliases for language: system / language: script (which will eventually be deprecated).

#3577 PR by @asottile.

Add support docker-in-docker detection for cgroups v2.

#3535 PR by @br-rhrbacek.

#3360 issue by @JasonAlt.

Fixes

Handle when docker gives SecurityOptions: null.

#3537 PR by @asottile.

#3514 issue by @jenstroeger.

Fix error context for invalid stages in .pre-commit-config.yaml.

#3576 PR by @asottile.

Changelog

Sourced from pre-commit's changelog.

4.4.0 - 2025-11-08

Features

Add --fail-fast option to pre-commit run.

#3528 PR by @JulianMaurin.

Upgrade ruby-build / rbenv.

#3566 PR by @asottile.

#3565 issue by @MRigal.

Add language: unsupported / language: unsupported_script as aliases for language: system / language: script (which will eventually be deprecated).

#3577 PR by @asottile.

Add support docker-in-docker detection for cgroups v2.

#3535 PR by @br-rhrbacek.

#3360 issue by @JasonAlt.

Fixes

Handle when docker gives SecurityOptions: null.

#3537 PR by @asottile.

#3514 issue by @jenstroeger.

Fix error context for invalid stages in .pre-commit-config.yaml.

#3576 PR by @asottile.

Commits

17cf886 v4.4.0
cb63a5c Merge pull request #3535 from br-rhrbacek/fix-cgroups
f80801d Fix docker-in-docker detection for cgroups v2
9143fc3 Merge pull request #3577 from pre-commit/language-unsupported
725acc9 rename system and script languages to unsupported / unsupported_script
3815e2e Merge pull request #3576 from pre-commit/fix-stages-config-error
aa2961c fix missing context in error for stages
46297f7 Merge pull request #3575 from pre-commit/rm-python3-hooks-repo
95eec75 rm python3_hooks_repo
5e4b354 Merge pull request #3574 from pre-commit/rm-hook-with-spaces-test
Additional commits viewable in compare view

Updates pytest from 8.4.2 to 9.0.0

Release notes

Sourced from pytest's releases.

9.0.0

pytest 9.0.0 (2025-11-05)

New features
#1367: Support for subtests has been added.

subtests <subtests> are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time.

Example:
def contains_docstring(p: Path) -> bool:
    """Return True if the given Python file contains a top-level docstring."""
    ...
def test_py_files_contain_docstring(subtests: pytest.Subtests) -> None:
for path in Path.cwd().glob("*.py"):
with subtests.test(path=str(path)):
assert contains_docstring(path)
Each assert failure or error is caught by the context manager and reported individually, giving a clear picture of all files that are missing a docstring.

In addition, unittest.TestCase.subTest is now also supported.

This feature was originally implemented as a separate plugin in pytest-subtests, but since then has been merged into the core.

[!NOTE] This feature is experimental and will likely evolve in future releases. By that we mean that we might change how subtests are reported on failure, but the functionality and how to use it are stable.
#13743: Added support for native TOML configuration files.

While pytest, since version 6, supports configuration in pyproject.toml files under [tool.pytest.ini_options], it does so in an "INI compatibility mode", where all configuration values are treated as strings or list of strings. Now, pytest supports the native TOML data model.

In pyproject.toml, the native TOML configuration is under the [tool.pytest] table.
# pyproject.toml
[tool.pytest]
minversion = "9.0"
addopts = ["-ra", "-q"]
testpaths = [
    "tests",
    "integration",
]

... (truncated)

Commits

f4b0fd2 Prepare release version 9.0.0
52d8e68 Merge pull request #13889 from bluetech/regendoc-restore
d6d3e4a doc: fixes for regendoc
7cb3974 doc: restore missing "# content of pytest.toml" regendoc commands
5ae9e47 build(deps): Bump django in /testing/plugins_integration (#13881)
adb3658 Merge pull request #13864 from bluetech/config-cleanups-2
a28c08e Merge pull request #13875 from bluetech/ci-tweaks
a250954 ci: split publish-to-pypi and push-tag jobs
ebc152f ci: update setup python's from 3.11 or 3.* to 3.13
dfd796f ci: move running update-plugin-list script to tox
Additional commits viewable in compare view

Updates python-semantic-release from 10.4.1 to 10.5.1

Release notes

Sourced from python-semantic-release's releases.

v10.5.1

[!WARNING] 2025-11-10: Release fails if --commit or commit: true when there are no files to commit for the version commit - Resolution in work

v10.5.1 (2025-11-10)

This release is published under the MIT License.

🪲 Bug Fixes

cmd-version: Fix upstream change detection to succeed without branch tracking (PR#1369, 7086257)

Detailed Changes: v10.5.0...v10.5.1

Installable artifacts are available from:

PyPi Registry

GitHub Release Assets

v10.5.0

[!WARNING] 2025-11-09: Release fails if active branch is not tracking a remote branch - Resolved in v10.5.1

v10.5.0 (2025-11-09)

This release is published under the MIT License.

✨ Features

cmd-version: Add automatic repository un-shallowing to version workflow (PR#1366, 90a1ffa)

cmd-version: Add functionality to create & update partial version tags (PR#1115, a28f940)

cmd-version: Adds c-macro style version definition support to version_variables (PR#1349, 4ce1fca)

cmd-version: Adds upstream check into workflow to prevent commit push collisions (PR#1360, d77193e)

🪲 Bug Fixes

cmd-version: Prevent regular expression errors on tag_format (PR#1367, e7d7aa7)

📖 Documentation

commands: Add description of automated upstream version checking upon version creation (PR#1360, d77193e)

... (truncated)

Changelog

Sourced from python-semantic-release's changelog.

v10.5.1 (2025-11-10)

🪲 Bug Fixes

cmd-version: Fix upstream change detection to succeed without branch tracking (PR#1369, 7086257)

.. _7086257: python-semantic-release/python-semantic-release@7086257 .. _PR#1369: python-semantic-release/python-semantic-release#1369

.. _changelog-v10.5.0:

v10.5.0 (2025-11-09)

✨ Features

cmd-version: Add automatic repository un-shallowing to version workflow (PR#1366, 90a1ffa)

cmd-version: Add functionality to create & update partial version tags (PR#1115, a28f940)

cmd-version: Adds c-macro style version definition support to version_variables, closes [#1348](https://github.com/python-semantic-release/python-semantic-release/issues/1348)_ (PR#1349, 4ce1fca)

cmd-version: Adds upstream check into workflow to prevent commit push collisions (PR#1360, d77193e)

🪲 Bug Fixes

cmd-version: Prevent regular expression errors on tag_format (PR#1367, e7d7aa7)

📖 Documentation

commands: Add description of automated upstream version checking upon version creation (PR#1360, d77193e)

configuration: Add description for add_partial_tags setting & usage examples (PR#1115, a28f940)

configuration: Fix tag_format definition (PR#1367, e7d7aa7)

configuration: Update version_variables examples with a c-macro style replacement

... (truncated)

Commits

bd8f84c chore: release v10.5.1
7086257 fix(cmd-version): fix upstream change detection to succeed without branch tra...
eb841f9 chore: release v10.5.0
a28f940 feat(cmd-version): add functionality to create & update partial version tags ...
e7d7aa7 fix(cmd-version): prevent regular expression errors on tag_format (#1367)
90a1ffa feat(cmd-version): add automatic repository un-shallowing to version workflow...
c95c608 ci(deps): bump mikepenz/action-junit-report@v6.0.0 action to v6.0.1 (#1361)
8b7077c chore(copilot): add GitHub Copilot instructions for repository (#1354)
2418719 chore(config): update PSR config to use conventional commit style version com...
a929dcf style(logging): remove type ignore for non error syntax
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

dependabot · 2025-11-10T10:06:04Z

Assignees

The following users could not be added as assignees: jonzeolla. Either the username does not exist or it does not have the correct permissions to be added as an assignee.

Labels

The following labels could not be found: dependencies, python. Please create them before Dependabot can add them to a pull request.

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

ai-coding-guardrails

Nice work! 😎

I didn't find anything of concern

List of skipped files due to configuration

uv.lock

Did you know Zenable also supports GitLab SaaS and self-managed?

Bumps the production-dependencies group with 4 updates: [coverage](https://github.com/coveragepy/coveragepy), [pre-commit](https://github.com/pre-commit/pre-commit), [pytest](https://github.com/pytest-dev/pytest) and [python-semantic-release](https://github.com/python-semantic-release/python-semantic-release). Updates `coverage` from 7.11.0 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.11.0...7.11.3) Updates `pre-commit` from 4.3.0 to 4.4.0 - [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.3.0...v4.4.0) Updates `pytest` from 8.4.2 to 9.0.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@8.4.2...9.0.0) Updates `python-semantic-release` from 10.4.1 to 10.5.1 - [Release notes](https://github.com/python-semantic-release/python-semantic-release/releases) - [Changelog](https://github.com/python-semantic-release/python-semantic-release/blob/master/CHANGELOG.rst) - [Commits](python-semantic-release/python-semantic-release@v10.4.1...v10.5.1) --- updated-dependencies: - dependency-name: coverage dependency-version: 7.11.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: production-dependencies - dependency-name: pre-commit dependency-version: 4.4.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: production-dependencies - dependency-name: pytest dependency-version: 9.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: production-dependencies - dependency-name: python-semantic-release dependency-version: 10.5.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: production-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot · 2025-12-15T09:27:24Z

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

dependabot bot assigned JonZeolla Nov 10, 2025

dependabot bot requested a review from JonZeolla as a code owner November 10, 2025 10:06

ai-coding-guardrails bot reviewed Nov 10, 2025

View reviewed changes

dependabot bot force-pushed the dependabot/uv/production-dependencies-ed59742445 branch from e08339b to 14d19c5 Compare December 8, 2025 09:30

dependabot bot closed this Dec 15, 2025

dependabot bot deleted the dependabot/uv/production-dependencies-ed59742445 branch December 15, 2025 09:27

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): bump the production-dependencies group with 4 updates #76

chore(deps): bump the production-dependencies group with 4 updates #76

Uh oh!

dependabot bot commented on behalf of github Nov 10, 2025 •

edited

Loading

Uh oh!

dependabot bot commented on behalf of github Nov 10, 2025

Uh oh!

ai-coding-guardrails bot left a comment

Uh oh!

dependabot bot commented on behalf of github Dec 15, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

chore(deps): bump the production-dependencies group with 4 updates #76

chore(deps): bump the production-dependencies group with 4 updates #76

Uh oh!

Conversation

dependabot bot commented on behalf of github Nov 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

7.11.3

Version 7.11.3 — 2025-11-09

7.11.2

Version 7.11.2 — 2025-11-08

7.11.1

Version 7.11.1 — 2025-11-07

7.11.1

Version 7.11.1 — 2025-11-07

Version 7.11.3 — 2025-11-09

Version 7.11.2 — 2025-11-08

Version 7.11.1 — 2025-11-07

pre-commit v4.4.0

Features

Fixes

4.4.0 - 2025-11-08

Features

Fixes

9.0.0

pytest 9.0.0 (2025-11-05)

New features

v10.5.1

v10.5.1 (2025-11-10)

🪲 Bug Fixes

v10.5.0

v10.5.0 (2025-11-09)

✨ Features

🪲 Bug Fixes

📖 Documentation

v10.5.1 (2025-11-10)

🪲 Bug Fixes

v10.5.0 (2025-11-09)

✨ Features

🪲 Bug Fixes

📖 Documentation

Uh oh!

dependabot bot commented on behalf of github Nov 10, 2025

Assignees

Labels

Uh oh!

ai-coding-guardrails bot left a comment

Choose a reason for hiding this comment

Uh oh!

dependabot bot commented on behalf of github Dec 15, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

dependabot bot commented on behalf of github Nov 10, 2025 •

edited

Loading