Bump the development-version-updates group with 4 updates by dependabot[bot] · Pull Request #294 · mrlonis/python-open-restaurant-fastapi

dependabot · 2025-11-10T12:38:34Z

Bumps the development-version-updates group with 4 updates: coverage, black, pre-commit and astroid.

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 black from 25.9.0 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)

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)

Commits

05f0a8c Prepare for 25.11.0 release (#4825)
ae17c61 Fix tests on pytest 9 (#4835)
138745e Include Windows and Python 3.14 in PR wheel build matrix, fix Windows build (...
18170d6 ci: add label for running all builds on a pull request (#4833)
0e793e3 fix windows wheels (#4830)
b71f36c Use build[uv] as cibuildwheel frontend (#4831)
a7bd594 Skip free threaded builds in cibuildwheel (#4829)
862dee9 Update cibuildwheel (#4828)
b5f354c build: restrict to pytest 9.0 due to breakage in custom pytest_configure (#4827)
f705197 t-string support (#4805)
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 astroid from 4.0.1 to 4.0.2

Release notes

Sourced from astroid's releases.

v4.0.2

What's New in astroid 4.0.2?

Release date: 2025-11-09

Handle FunctionDef blockstart_tolineno edge cases correctly.

Refs #2880

Add HTTPMethod enum support to brain module for Python 3.11+.

Refs pylint-dev/pylint#10624 Closes #2877

Changelog

Sourced from astroid's changelog.

What's New in astroid 4.0.2?

Release date: 2025-11-09

Handle FunctionDef blockstart_tolineno edge cases correctly.

Refs #2880

Add HTTPMethod enum support to brain module for Python 3.11+.

Refs pylint-dev/pylint#10624 Closes #2877

Commits

a068430 Bump astroid to 4.0.2, update changelog
a5ce4b0 Upgrade pylint to 4.0.0, add mypy to the allowlist
d71bfac [Backport maintenance/4.0.x] Handle FunctionDef blockstart_tolineno edge case...
e127630 [Backport maintenance/4.0.x] feat: add HTTPMethod enum support to brain_http ...
See full diff 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

Bumps the development-version-updates group with 4 updates: [coverage](https://github.com/coveragepy/coveragepy), [black](https://github.com/psf/black), [pre-commit](https://github.com/pre-commit/pre-commit) and [astroid](https://github.com/pylint-dev/astroid). 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 `black` from 25.9.0 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 `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 `astroid` from 4.0.1 to 4.0.2 - [Release notes](https://github.com/pylint-dev/astroid/releases) - [Changelog](https://github.com/pylint-dev/astroid/blob/main/ChangeLog) - [Commits](pylint-dev/astroid@v4.0.1...v4.0.2) --- updated-dependencies: - dependency-name: coverage dependency-version: 7.11.3 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: development-version-updates - dependency-name: black dependency-version: 25.11.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development-version-updates - dependency-name: pre-commit dependency-version: 4.4.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development-version-updates - dependency-name: astroid dependency-version: 4.0.2 dependency-type: indirect update-type: version-update:semver-patch dependency-group: development-version-updates ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Nov 10, 2025

dependabot bot force-pushed the dependabot/pip/development-version-updates-dc6cb76d94 branch from 48fc0f4 to 449bdd1 Compare November 10, 2025 14:43

github-actions bot approved these changes Nov 10, 2025

View reviewed changes

github-actions bot enabled auto-merge November 10, 2025 14:44

github-actions bot merged commit a133459 into main Nov 10, 2025
4 checks passed

github-actions bot deleted the dependabot/pip/development-version-updates-dc6cb76d94 branch November 10, 2025 14:45

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bump the development-version-updates group with 4 updates#294

Bump the development-version-updates group with 4 updates#294
github-actions[bot] merged 1 commit intomainfrom
dependabot/pip/development-version-updates-dc6cb76d94

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

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

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

25.11.0

Highlights

Stable style

Preview style

Configuration

Packaging

Output

Blackd

Integrations

25.11.0

Highlights

Stable style

Preview style

Configuration

Packaging

Output

Blackd

Integrations

pre-commit v4.4.0

Features

Fixes

4.4.0 - 2025-11-08

Features

Fixes

v4.0.2

What's New in astroid 4.0.2?

What's New in astroid 4.0.2?

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

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

edited

Loading