fix(deps) Update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence	Type	Update
@semantic-release/commit-analyzer	13.0.0 -> 13.0.1			devDependencies	patch
@semantic-release/github	11.0.1 -> 11.0.6			devDependencies	patch
@semantic-release/npm	12.0.1 -> 12.0.2			devDependencies	patch
@semantic-release/release-notes-generator	14.0.2 -> 14.1.0			devDependencies	minor
JRubics/poetry-publish	v2.0 -> v2.1			action	minor
asottile/pyupgrade	v3.19.1 -> v3.21.0			repository	minor
black (changelog)	23.3.0 -> 23.12.1			dev	minor
coverage	7.2.7 -> 7.11.0			dev	minor
isort (changelog)	5.11.5 -> 5.13.2			dev	minor
macisamuele/language-formatters-pre-commit-hooks	v2.14.0 -> v2.15.0			repository	minor
mypy (changelog)	1.4.1 -> 1.18.2			dev	minor
python	3.10 -> 3.14			uses-with	minor
semantic-release	24.2.0 -> 24.2.9			devDependencies	patch
tox (changelog)	4.8.0 -> 4.31.0			dev	minor

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.

---

Release Notes

semantic-release/commit-analyzer (@​semantic-release/commit-analyzer)

v13.0.1

Compare Source

Bug Fixes

• deps: update dependency import-from-esm to v2 (#​741) (f106b76)

semantic-release/github (@​semantic-release/github)

v11.0.6

Compare Source

Bug Fixes

• deps: switch to tinyglobby (#​1041) (ed90698)

v11.0.5

Compare Source

Bug Fixes

• remove github search api consumption (#​1086) (95ea166)

v11.0.4

Compare Source

Bug Fixes

• Check failCommentCondition in "success" step (#​1026) (d77b6f4)

v11.0.3

Compare Source

Bug Fixes

• deps: update octokit monorepo (major) (#​1049) (b60a983)

v11.0.2

Compare Source

Bug Fixes

• deps: update octokit monorepo (major) (#​1020) (12f6bfd)

semantic-release/npm (@​semantic-release/npm)

v12.0.2

Compare Source

Bug Fixes

• deps: update npm to ^10.9.3 (#​972) (93e0937)

semantic-release/release-notes-generator (@​semantic-release/release-notes-generator)

v14.1.0

Compare Source

Features

• preset: support ignoreCommits option (#​836) (485bc0a)

v14.0.3

Compare Source

Bug Fixes

• deps: update dependency import-from-esm to v2 (#​756) (832620e)

JRubics/poetry-publish (JRubics/poetry-publish)

v2.1: Support latest python versions

Compare Source

asottile/pyupgrade (asottile/pyupgrade)

v3.21.0

Compare Source

v3.20.0

Compare Source

psf/black (black)

v23.12.1

Compare Source

Packaging

• Fixed a bug that included dependencies from the d extra by default (#​4108)

v23.12.0

Compare Source

Highlights

It's almost 2024, which means it's time for a new edition of Black's stable style!
Together with this release, we'll put out an alpha release 24.1a1 showcasing the draft
2024 stable style, which we'll finalize in the January release. Please try it out and
share your feedback.

This release (23.12.0) will still produce the 2023 style. Most but not all of the
changes in --preview mode will be in the 2024 stable style.

Stable style

• Fix bug where # fmt: off automatically dedents when used with the --line-ranges
  option, even when it is not within the specified line range. (#​4084)
• Fix feature detection for parenthesized context managers (#​4104)

Preview style

• Prefer more equal signs before a break when splitting chained assignments (#​4010)
• Standalone form feed characters at the module level are no longer removed (#​4021)
• Additional cases of immediately nested tuples, lists, and dictionaries are now
  indented less (#​4012)
• Allow empty lines at the beginning of all blocks, except immediately before a
  docstring (#​4060)
• Fix crash in preview mode when using a short --line-length (#​4086)
• Keep suites consisting of only an ellipsis on their own lines if they are not
  functions or class definitions (#​4066) (#​4103)

Configuration

• --line-ranges now skips Black's internal stability check in --safe mode. This
  avoids a crash on rare inputs that have many unformatted same-content lines. (#​4034)

Packaging

• Upgrade to mypy 1.7.1 (#​4049) (#​4069)
• Faster compiled wheels are now available for CPython 3.12 (#​4070)

Integrations

• Enable 3.12 CI (#​4035)
• Build docker images in parallel (#​4054)
• Build docker images with 3.12 (#​4055)

v23.11.0

Compare Source

Highlights

• Support formatting ranges of lines with the new --line-ranges command-line option
  (#​4020)

Stable style

• Fix crash on formatting bytes strings that look like docstrings (#​4003)
• Fix crash when whitespace followed a backslash before newline in a docstring (#​4008)
• Fix standalone comments inside complex blocks crashing Black (#​4016)
• Fix crash on formatting code like await (a ** b) (#​3994)
• No longer treat leading f-strings as docstrings. This matches Python's behaviour and
  fixes a crash (#​4019)

Preview style

• Multiline dicts and lists that are the sole argument to a function are now indented
  less (#​3964)
• Multiline unpacked dicts and lists as the sole argument to a function are now also
  indented less (#​3992)
• In f-string debug expressions, quote types that are visible in the final string are
  now preserved (#​4005)
• Fix a bug where long case blocks were not split into multiple lines. Also enable
  general trailing comma rules on case blocks (#​4024)
• Keep requiring two empty lines between module-level docstring and first function or
  class definition (#​4028)
• Add support for single-line format skip with other comments on the same line (#​3959)

Configuration

• Consistently apply force exclusion logic before resolving symlinks (#​4015)
• Fix a bug in the matching of absolute path names in --include (#​3976)

Performance

• Fix mypyc builds on arm64 on macOS (#​4017)

Integrations

• Black's pre-commit integration will now run only on git hooks appropriate for a code
  formatter (#​3940)

v23.10.1

Compare Source

Highlights

• Maintenance release to get a fix out for GitHub Action edge case (#​3957)

Preview style

• Fix merging implicit multiline strings that have inline comments (#​3956)
• Allow empty first line after block open before a comment or compound statement (#​3967)

Packaging

• Change Dockerfile to hatch + compile black (#​3965)

Integrations

• The summary output for GitHub workflows is now suppressible using the summary
  parameter. (#​3958)
• Fix the action failing when Black check doesn't pass (#​3957)

Documentation

• It is known Windows documentation CI is broken
  #​3968

v23.10.0

Compare Source

Stable style

• Fix comments getting removed from inside parenthesized strings (#​3909)

Preview style

• Fix long lines with power operators getting split before the line length (#​3942)
• Long type hints are now wrapped in parentheses and properly indented when split across
  multiple lines (#​3899)
• Magic trailing commas are now respected in return types. (#​3916)
• Require one empty line after module-level docstrings. (#​3932)
• Treat raw triple-quoted strings as docstrings (#​3947)

Configuration

• Fix cache versioning logic when BLACK_CACHE_DIR is set (#​3937)

Parser

• Fix bug where attributes named type were not accepted inside match statements
  (#​3950)
• Add support for PEP 695 type aliases containing lambdas and other unusual expressions
  (#​3949)

Output

• Black no longer attempts to provide special errors for attempting to format Python 2
  code (#​3933)
• Black will more consistently print stacktraces on internal errors in verbose mode
  (#​3938)

Integrations

• The action output displayed in the job summary is now wrapped in Markdown (#​3914)

v23.9.1

Compare Source

Due to various issues, the previous release (23.9.0) did not include compiled mypyc
wheels, which make Black significantly faster. These issues have now been fixed, and
this release should come with compiled wheels once again.

There will be no wheels for Python 3.12 due to a bug in mypyc. We will provide 3.12
wheels in a future release as soon as the mypyc bug is fixed.

Packaging

• Upgrade to mypy 1.5.1 (#​3864)

Performance

• Store raw tuples instead of NamedTuples in Black's cache, improving performance and
  decreasing the size of the cache (#​3877)

v23.9.0

Compare Source

Preview style

• More concise formatting for dummy implementations (#​3796)
• In stub files, add a blank line between a statement with a body (e.g an
  if sys.version_info > (3, x):) and a function definition on the same level (#​3862)
• Fix a bug whereby spaces were removed from walrus operators within subscript(#​3823)

Configuration

• Black now applies exclusion and ignore logic before resolving symlinks (#​3846)

Performance

• Avoid importing IPython if notebook cells do not contain magics (#​3782)
• Improve caching by comparing file hashes as fallback for mtime and size (#​3821)

Blackd

• Fix an issue in blackd with single character input (#​3558)

Integrations

• Black now has an
  official pre-commit mirror. Swapping
  https://github.com/psf/black to https://github.com/psf/black-pre-commit-mirror in
  your .pre-commit-config.yaml will make Black about 2x faster (#​3828)
• The .black.env folder specified by ENV_PATH will now be removed on the completion
  of the GitHub Action (#​3759)

v23.7.0

Compare Source

Highlights

• Runtime support for Python 3.7 has been removed. Formatting 3.7 code will still be
  supported until further notice (#​3765)

Stable style

• Fix a bug where an illegal trailing comma was added to return type annotations using
  PEP 604 unions (#​3735)
• Fix several bugs and crashes where comments in stub files were removed or mishandled
  under some circumstances (#​3745)
• Fix a crash with multi-line magic comments like type: ignore within parentheses
  (#​3740)
• Fix error in AST validation when Black removes trailing whitespace in a type comment
  (#​3773)

Preview style

• Implicitly concatenated strings used as function args are no longer wrapped inside
  parentheses (#​3640)
• Remove blank lines between a class definition and its docstring (#​3692)

Configuration

• The --workers argument to Black can now be specified via the BLACK_NUM_WORKERS
  environment variable (#​3743)
• .pytest_cache, .ruff_cache and .vscode are now excluded by default (#​3691)
• Fix Black not honouring pyproject.toml settings when running --stdin-filename
  and the pyproject.toml found isn't in the current working directory (#​3719)
• Black will now error if exclude and extend-exclude have invalid data types in
  pyproject.toml, instead of silently doing the wrong thing (#​3764)

Packaging

• Upgrade mypyc from 0.991 to 1.3 (#​3697)
• Remove patching of Click that mitigated errors on Python 3.6 with LANG=C (#​3768)

Parser

• Add support for the new PEP 695 syntax in Python 3.12 (#​3703)

Performance

• Speed up Black significantly when the cache is full (#​3751)
• Avoid importing IPython in a case where we wouldn't need it (#​3748)

Output

• Use aware UTC datetimes internally, avoids deprecation warning on Python 3.12 (#​3728)
• Change verbose logging to exactly mirror Black's logic for source discovery (#​3749)

Blackd

• The blackd argument parser now shows the default values for options in their help
  text (#​3712)

Integrations

• Black is now tested with
  PYTHONWARNDEFAULTENCODING = 1
  (#​3763)
• Update GitHub Action to display black output in the job summary (#​3688)

Documentation

• Add a CITATION.cff file to the root of the repository, containing metadata on how to
  cite this software (#​3723)
• Update the classes and exceptions documentation in Developer reference to match
  the latest code base (#​3755)

nedbat/coveragepy (coverage)

v7.11.0

Compare Source

• Dropped support for Python 3.9, declared support for Python 3.15 alpha.

.. _changes_7-10-7:

v7.10.7

Compare Source

• Performance: with branch coverage in large files, generating HTML, JSON, or
  LCOV reports could take far too long due to some quadratic behavior when
  creating the function and class index pages. This is now fixed, closing
  issue 2048_. Thanks to Daniel Diniz for help diagnosing the problem.

• Most warnings and a few errors now have links to a page in the docs
  explaining the specific message. Closes issue 1921_.

.. _issue 1921: #​1921
.. _issue 2048: #​2048

.. _changes_7-10-6:

v7.10.6

Compare Source

• Fix: source directories were not properly communicated to subprocesses
  that ran in different directories, as reported in issue 1499_. This is now
  fixed.

• Performance: Alex Gaynor continues fine-tuning <pull 2038_>_ the speed of
  combination, especially with many contexts.

.. _issue 1499: #​1499
.. _pull 2038: #​2038

.. _changes_7-10-5:

v7.10.5

Compare Source

• Big speed improvements for coverage combine: it's now about twice as
  fast! Huge thanks to Alex Gaynor for pull requests 2032 <pull 2032_>,
  2033 <pull 2033_>, and 2034 <pull 2034_>_.

.. _pull 2032: #​2032
.. _pull 2033: #​2033
.. _pull 2034: #​2034

.. _changes_7-10-4:

v7.10.4

Compare Source

• Added patch = fork for times when the built-in forking support is
  insufficient.

• Fix: patch = execv also inherits the entire coverage configuration now.

.. _changes_7-10-3:

v7.10.3

Compare Source

• Fixes for patch = subprocess:

  • If subprocesses spawned yet more subprocesses simultaneously, some coverage
    could be missed. This is now fixed, closing issue 2024_.

  • If subprocesses were created in other directories, their data files were
    stranded there and not combined into the totals, as described in issue 2025_. This is now fixed.

  • On Windows (or maybe only some Windows?) the patch would fail with a
    ModuleNotFound error trying to import coverage. This is now fixed,
    closing issue 2022_.

  • Originally only options set in the coverage configuration file would apply
    to subprocesses. Options set on the coverage run command line (such as
    --branch) wouldn't be communicated to the subprocesses. This could
    lead to combining failures, as described in issue 2021_. Now the entire
    configuration is used in subprocesses, regardless of its origin.

  • Added debug=patch to help diagnose problems.

• Fix: really close all SQLite databases, even in-memory ones. Closes issue 2017_.

.. _issue 2017: #​2017
.. _issue 2021: #​2021
.. _issue 2022: #​2022
.. _issue 2024: #​2024
.. _issue 2025: #​2025

.. _changes_7-10-2:

v7.10.2

Compare Source

• Fix: some code with NOP bytecodes could report missing branches that are
  actually executed. This is now fixed, closing issue 1999_. Python 3.9
  still shows the problem.

.. _issue 1999: #​1999

.. _changes_7-10-1:

v7.10.1

Compare Source

• Fix: the exclusion for if TYPE_CHECKING: was wrong: it marked the branch
  as partial, but it should have been a line exclusion so the entire clause
  would be excluded. Improves issue 831_.

• Fix: changed where .pth files are written for patch = subprocess, closing
  issue 2006_.

.. _issue 2006: #​2006

.. _changes_7-10-0:

v7.10.0

Compare Source

• A new configuration option: ":ref:config_run_patch" specifies named patches
  to work around some limitations in coverage measurement. These patches are
  available:

  • patch = _exit lets coverage save its data even when :func:os._exit() <python:os._exit> is used to abruptly end the process. This closes
    long-standing issue 310_ as well as its duplicates: issue 312, issue 1673, issue 1845, and issue 1941.

  • patch = subprocess measures coverage in Python subprocesses created
    with :mod:subprocess, :func:os.system, or one of the :func:execv <python:os.execl> or :func:spawnv <python:os.spawnl> family of
    functions. Closes old issue 367, its duplicate issue 378 and old
    issue 689_.

  • patch = execv adjusts the :func:execv <python:os.execl> family of
    functions to save coverage data before ending the current program and
    starting the next. Not available on Windows. Closes issue 43_ after 15
    years!

• The HTML report now dimly colors subsequent lines in multi-line statements.
  They used to have no color. This gives a better indication of the amount of
  code missing in the report. Closes issue 1308_.

• Two new exclusion patterns are part of the defaults: ... is automatically
  excluded as a line and if TYPE_CHECKING: is excluded as a branch. Closes
  issue 831_.

• A new command-line option: --save-signal=USR1 specifies a signal that
  coverage.py will listen for. When the signal is sent, the coverage data will
  be saved. This makes it possible to save data from within long-running
  processes. Thanks, Arkady Gilinsky <pull 1998_>_.

• A new configuration option: ":ref:config_report_partial_also" is a list of
  regexes to add as pragmas for partial branches. This parallels the
  ":ref:config_report_exclude_also" setting for adding line exclusion
  patterns.

• A few file path configuration settings didn't allow for tilde expansion:
  :ref:config_json_output, :ref:config_lcov_output and
  :ref:config_run_debug_file. This is now fixed.

• Wheels are included for 3.14 now that 3.14 rc1 is available.

• We no longer ship a PyPy-specific wheel. PyPy will install the pure-Python
  wheel. Closes issue 2001_.

• In the very unusual situation of not having a current frame, coverage no
  longer crashes when using the sysmon core, fixing issue 2005_.

.. _issue 43: #​43
.. _issue 310: #​310
.. _issue 312: #​312
.. _issue 367: #​367
.. _issue 378: #​378
.. _issue 689: #​689
.. _issue 831: #​831
.. _issue 1308: #​1308
.. _issue 1673: #​1673
.. _issue 1845: #​1845
.. _issue 1941: #​1941
.. _pull 1998: #​1998
.. _issue 2001: #​2001
.. _issue 2005: #​2005

.. _changes_7-9-2:

v7.9.2

Compare Source

• Fix: complex conditionals within a line might cause a KeyError when using
  sys.monitoring, as reported in issue 1991_. This is now fixed.

• Fix: we can now measure coverage for code in Python archive (.par) files.
  Thanks, Itamer Oren <pull 1984_>_.

.. _pull 1984: #​1984
.. _issue 1991: #​1991

.. _changes_7-9-1:

v7.9.1

Compare Source

• The "no-ctracer" warning is not issued for Python pre-release versions.
  Coverage doesn't ship compiled wheels for those versions, so this was far too
  noisy.

• On Python 3.14+, the "sysmon" core is now the default if it's supported for
  your configuration. Plugins and dynamic contexts are still not supported
  with it.

.. _changes_7-9-0:

v7.9.0

Compare Source

• Added a [run] core configuration setting to specify the measurement core,
  which was previously only available through the COVERAGE_CORE environment
  variable. Finishes issue 1746_.

• Fixed incorrect rendering of f-strings with doubled braces, closing issue 1980_.

• If the C tracer core can't be imported, a warning ("no-ctracer") is issued
  with the reason.

• The C tracer core extension module now conforms to PEP 489, closing issue 1977. Thanks, Adam Turner <pull 1978_>_.

• Fixed a "ValueError: min() arg is an empty sequence" error caused by strange
  empty modules, found by oss-fuzz_.

.. _issue 1746: #​1746
.. _issue 1977: #​1977
.. _pull 1978: #​1978
.. _issue 1980: #​1980
.. _PEP 489: https://peps.python.org/pep-0489
.. _oss-fuzz: https://google.github.io/oss-fuzz/

.. _changes_7-8-2:

v7.8.2

Compare Source

• Wheels are provided for Windows ARM64 on Python 3.11, 3.12, and 3.13.
  Thanks, Finn Womack <pull 1972_>_.

.. _issue 1971: #​1971
.. _pull 1972: #​1972

.. _changes_7-8-1:

v7.8.1

Compare Source

• A number of EncodingWarnings were fixed that could appear if you've enabled
  PYTHONWARNDEFAULTENCODING, fixing issue 1966. Thanks, Henry Schreiner <pull 1967_>.

• Fixed a race condition when using sys.monitoring with free-threading Python,
  closing issue 1970_.

.. _issue 1966: #​1966
.. _pull 1967: #​1967
.. _issue 1970: #​1970

.. _changes_7-8-0:

v7.8.0

Compare Source

• Added a new source_dirs setting for symmetry with the existing
  source_pkgs setting. It's preferable to the existing source setting,
  because you'll get a clear error when directories don't exist. Fixes issue 1942. Thanks, Jeremy Fleischman <pull 1943_>.

• Fix: the PYTHONSAFEPATH environment variable new in Python 3.11 is properly
  supported, closing issue 1696. Thanks, Philipp A. <pull 1700_>. This
  works properly except for a detail when using the coverage command on
  Windows. There you can use python -m coverage instead if you need exact
  emulation.

.. _issue 1696: #​1696
.. _pull 1700: #​1700
.. _issue 1942: #​1942
.. _pull 1943: #​1943

.. _changes_7-7-1:

v7.7.1

Compare Source

• A few small tweaks to the sys.monitoring support for Python 3.14. Please
  test!

.. _changes_7-7-0:

v7.7.0

Compare Source

• The Coverage object has a new method, :meth:.Coverage.branch_stats for
  getting simple branch information for a module. Closes issue 1888_.

• The :class:Coverage constructor<.Coverage> now has a plugins parameter
  for passing in plugin objects directly, thanks to Alex Gaynor <pull 1919_>_.

• Many constant tests in if statements are now recognized as being optimized
  away. For example, previously if 13: would have been considered a branch
  with one path not taken. Now it is understood as always true and no coverage
  is missing.

• The experimental sys.monitoring support now works for branch coverage if you
  are using Python 3.14.0 alpha 6 or newer. This should reduce the overhead
  coverage.py imposes on your test suite. Set the environment variable
  COVERAGE_CORE=sysmon to try it out.

• Confirmed support for PyPy 3.11. Thanks Michał Górny.

.. _issue 1888: #​1888
.. _pull 1919: #​1919

.. _changes_7-6-12:

v7.6.12

Compare Source

• Fix: some aarch64 distributions were missing (issue 1927_). These are now
  building reliably.

.. _issue 1927: #​1927

.. _changes_7-6-11:

v7.6.11

Compare Source

• Fix: a memory leak in CTracer has been fixed. The details are in issue 1924_ and pytest-dev 676_. This should reduce the memory footprint for
  everyone even if it hadn't caused a problem before.

• We now ship a py3-none-any.whl wheel file. Thanks, Russell Keith-Magee <pull 1914_>_.

.. _pull 1914: #​1914
.. _issue 1924: #​1924
.. _pytest-dev 676: pytest-dev/pytest-cov#676

.. _changes_7-6-10:

v7.6.10

Compare Source

• Fix: some descriptions of missing branches in HTML and LCOV reports were
  incorrect when multi-line statements were involved (issue 1874_ and issue 1875_). These are now fixed.

• Fix: Python 3.14 defers evaluation of annotations <pep649_>_ by moving them
  into separate code objects. That code is rarely executed, so coverage.py
  would mark them as missing, as reported in issue 1908_. Now they are
  ignored by coverage automatically.

• Fixed an obscure and mysterious problem on PyPy 3.10 seemingly involving
  mocks, imports, and trace functions: issue 1902_. To be honest, I don't
  understand the problem or the solution, but git bisect helped find it,
  and now it's fixed.

• Docs: re-wrote the :ref:subprocess page to put multiprocessing first and to
  highlight the correct use of :class:multiprocessing.Pool <python:multiprocessing.pool.Pool>.

.. _issue 1874: #​1874
.. _issue 1875: #​1875
.. _issue 1902: #​1902
.. _issue 1908: #​1908
.. _pep649: https://docs.python.org/3.14/whatsnew/3.14.html#whatsnew314-deferred-annotations

.. _changes_7-6-9:

v7.6.9

Compare Source

• Fix: Tomas Uribe fixed <pull 1901_>_ a performance problem in the XML
  report. Large code bases should produce XML reports much faster now.

.. _pull 1901: #​1901

.. _changes_7-6-8:

v7.6.8

Compare Source

• Fix: the LCOV report code assumed that a branch line that took no branches
  meant that the entire line was unexecuted. This isn't true in a few cases:
  the line might always raise an exception, or might have been optimized away.
  Fixes issue 1896_.

• Fix: similarly, the HTML report will now explain that a line that jumps to
  none of its expected destinations must have always raised an exception.
  Previously, it would say something nonsensical like, "line 4 didn't jump to
  line 5 because line 4 was never true, and it didn't jump to line 7 because
  line 4 was always true." This was also shown in issue 1896_.

.. _issue 1896: #​1896

.. _changes_7-6-7:

v7.6.7

Compare Source

• Fix: ugh, the other assert from 7.6.5 can also be encountered in the wild,
  so it's been restored to a conditional. Sorry for the churn.

.. _changes_7-6-6:

v7.6.6

Compare Source

• One of the new asserts from 7.6.5 caused problems in real projects, as
  reported in issue 1891_. The assert has been removed.

.. _issue 1891: #​1891

.. _changes_7-6-5:

v7.6.5

Compare Source

• Fix: fine-tuned the exact Python version (3.12.6) when exiting from with
  statements changed how they traced. This affected whether people saw the
  fix for issue 1880_.

• Fix: isolate our code more from mocking in the os module that in rare cases
  can cause bizarre behavior <pytest-cov-666_>_.

• Refactor: some code unreachable code paths in parser.py were changed to
  asserts. If you encounter any of these, please let me know!

.. _pytest-cov-666: pytest-dev/pytest-cov#666

.. _changes_7-6-4:

v7.6.4

Compare Source

• Fix: multi-line with statements could cause contained branches to be
  incorrectly marked as missing (issue 1880_). This is now fixed.

.. _issue 1880: #​1880

.. _changes_7-6-3:

v7.6.3

Compare Source

• Fix: nested context managers could incorrectly be analyzed to flag a missing
  branch on the last context manager, as described in issue 1876_. This is
  now fixed.

• Fix: the missing branch message about not exiting a module had an extra
  "didn't," as described in issue 1873_. This is now fixed.

.. _issue 1873: #​1873
.. _issue 1876: #​1876

.. _changes_7-6-2:

v7.6.2

Compare Source

• Dropped support for Python 3.8 and PyPy 3.8.

• Fix: a final wildcard match/case clause assigning to a name (case _ as value) was incorrectly marked as a missing branch. This is now fixed,
  closing issue 1860_.

• Fewer things are considered branches now. Lambdas, comprehensions, and
  generator expressions are no longer marked as missing branches if they don't
  complete execution. Closes issue 1852_.

• Fix: the HTML report didn't properly show multi-line f-strings that end with
  a backslash continuation. This is now fixed, closing issue 1836, thanks
  to LiuYinCarl and Marco Ricci <pull 1838_>.

• Fix: the LCOV report now has correct line numbers (fixing issue 1846) and
  better branch descriptions for BRDA records (fixing issue 1850). There
  are other changes to lcov also, including a new configuration option
  :ref:line_checksums <config_lcov_line_checksums> to control whether line
  checksums are included in the lcov report. The default is false. To keep
  checksums set it to true. All this work is thanks to Zack Weinberg
  (pull 1849_ and pull 1851_).

• Fixed the docs for multi-line regex exclusions, closing issue 1863_.

• Fixed a potential crash in the C tracer, closing issue 1835, thanks to
  Jan Kühle <pull 1843_>.

.. _issue 1835: #​1835
.. _issue 1836: #​1836
.. _pull 1838: #​1838
.. _pull 1843: #​1843
.. _issue 1846: #​1846
.. _pull 1849: #​1849
.. _issue 1850: #​1850
.. _pull 1851: #​1851
.. _issue 1852: #​1852
.. _issue 1860: #​1860
.. _issue 1863: #​1863

.. _changes_7-6-1:

v7.6.1

Compare Source

• Fix: some aarch64 distributions were missing (issue 1927_). These are now
  building reliably.

.. _issue 1927: #​1927

.. _changes_7-6-11:

v7.6.0

Compare Source

• Exclusion patterns can now be multi-line, thanks to Daniel Diniz <pull 1807_>. This enables many interesting exclusion use-cases, including those
  requested in issues 118 <issue 118_> (entire files), 996 <issue 996_>_ (multiple lines only when appearing together), 1741 <issue 1741_>_ (remainder of a function), and 1803 <issue 1803_>_
  (arbitrary sequence of marked lines). See the :ref:multi_line_exclude
  section of the docs for more details and examples.

• The JSON report now includes per-function and per-class coverage information.
  Thanks to Daniel Diniz <pull 1809_>_ for getting the work started. This
  closes issue 1793_ and issue 1532_.

• Fixed an incorrect calculation of "(no class)" lines in the HTML classes
  report.

• Python 3.13.0b3 is supported.

.. _issue 118: #​118
.. _issue 996: #​996
.. _issue 1532: #​1532
.. _issue 1741: #​1741
.. _issue 1793: #​1793
.. _issue 1803: #​1803
.. _pull 1807: #​1807
.. _pull 1809: #​1809

.. _changes_7-5-4:

v7.5.4

Compare Source

• If you attempt to combine statement coverage data with branch coverage data,
  coverage.py used to fail with the message "Can't combine arc data with line
  data" or its reverse, "Can't combine line data with arc data." These
  messages used internal terminology, making it hard for people to understand
  the problem. They are now changed to mention "branch coverage data" and
  "statement coverage data."

• Fixed a minor branch coverage problem with wildcard match/case cases using
  names or

---

Configuration

📅 Schedule: Branch creation - "before 10pm on Sunday" in timezone America/Chicago, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.