Repository navigation
chore(deps): update all dependencies - #809
renovate[bot] wants to merge 1 commit into
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
| Check name | Status | Explanation |
|---|---|---|
| Description Check | ✅ Passed | Check skipped - CodeRabbit’s high-level summary is enabled. |
| Title check | ✅ Passed | The title clearly identifies the pull request as a dependency update. It matches the stated objective and the listed changes. |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| Linked Issues check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
Finishing Touches
ℹ️ Recent review info
-
⚙️ Run configuration
-
Configuration used: Organization UI
Review profile: CHILL
Plan: Enterprise
Run ID: 6942a334-05f9-4416-a361-340a75c6852b
⛔ Files ignored due to path filters (1)
-
uv.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
-
.pre-commit-config.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
-
- .pre-commit-config.yaml
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.
ℹ️ Recent review info
-
⚙️ Run configuration
-
Configuration used: Organization UI
Review profile: CHILL
Plan: Enterprise
Run ID:
6942a334-05f9-4416-a361-340a75c6852b
⛔ Files ignored due to path filters (1)
-
uv.lockis excluded by!**/*.lock
📒 Files selected for processing (1)
-
.pre-commit-config.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
-
- .pre-commit-config.yaml
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.
-
c021384 to
37ab0af
Compare
de0d64e to
938209b
Compare
2902d62 to
def67e5
Compare
4f88692 to
9a0179c
Compare
|
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
3.1.1→3.2.03.1.1→3.2.026.9.0→26.11.026.9.0→26.11.026.9.0→26.11.026.9.0→26.11.026.9.0→26.11.00.12.5→0.13.9v2.5.8→v2.6.87.16.1→7.17.37.17.45.2.17→5.2.196.1.1→6.1.226.2.0→27.0.10.9.1→0.12.0==36.0.3→==37.0.237.0.326.9.0→26.11.0==26.7.15→==26.11.02.3.1→2.4.126.2.1→26.31.17.6→1.18.190.5.3→0.5.110.9.1→0.12.04.0.9→4.1.49.1.1→9.2.09.1.1→9.2.026.9.0→26.11.03.14→3.150.16.9→0.17.61.5.5→1.11.34.64.2→4.67.1526.9.0→26.11.01.36.0→1.37.96.0.12.20260906→6.0.12.202611136.0.12.202611222.33.0.20260906→2.33.0.2026103024.04→26.04Note: The
pre-commitmanager in Renovate is not supported by thepre-commitmaintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.Release Notes
ansible/ansible-builder (ansible-builder)
v3.2.0Compare Source
What's Changed
additional_build_filesfile copies.bindep.See the porting guide for version 3.2 for more details.
ansible/ansible-compat (ansible-compat)
v26.11.0Compare Source
What's Changed
Full Changelog: ansible/ansible-compat@v26.10.0...v26.11.0
v26.10.0Compare Source
What's Changed
Full Changelog: ansible/ansible-compat@v26.9.0...v26.10.0
ansible/ansible-creator (ansible-creator)
v26.11.0Compare Source
What's Changed
Full Changelog: ansible/ansible-creator@v26.10.0...v26.11.0
v26.10.0Compare Source
What's Changed
Full Changelog: ansible/ansible-creator@v26.9.0...v26.10.0
ansible/ansible-dev-environment (ansible-dev-environment)
v26.11.0Compare Source
What's Changed
Full Changelog: ansible/ansible-dev-environment@v26.10.0...v26.11.0
v26.10.0Compare Source
What's Changed
Full Changelog: ansible/ansible-dev-environment@v26.9.0...v26.10.0
ansible/ansible-lint (ansible-lint)
v26.11.0Compare Source
What's Changed
New Contributors
Full Changelog: ansible/ansible-lint@v26.10.1...v26.11.0
v26.10.1Compare Source
What's Changed
Full Changelog: ansible/ansible-lint@v26.10.0...v26.10.1
v26.10.0Compare Source
What's Changed
New Contributors
Full Changelog: ansible/ansible-lint@v26.9.0...v26.10.0
ansible/ansible-navigator (ansible-navigator)
v26.11.0Compare Source
What's Changed
New Contributors
Full Changelog: ansible/ansible-navigator@v26.10.0...v26.11.0
v26.10.0Compare Source
What's Changed
New Contributors
Full Changelog: ansible/ansible-navigator@v26.8.0...v26.10.0
astral-sh/uv-pre-commit
v0.13.9Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.13.9
v0.13.8Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.13.8
v0.13.7Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.13.7
v0.13.6Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.13.6
v0.13.5Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.13.5
v0.13.4Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.13.4
v0.13.3Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.13.3
v0.13.2Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.13.2
v0.13.1Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.13.1
v0.13.0Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.13.0
v0.12.24Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.24
v0.12.23Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.23
v0.12.22Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.22
v0.12.21Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.21
v0.12.20Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.20
v0.12.19Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.19
v0.12.18Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.18
v0.12.17Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.17
v0.12.16Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.16
v0.12.15Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.15
v0.12.14Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.14
v0.12.13Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.13
v0.12.12Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.12
v0.12.11Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.11
v0.12.10Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.10
v0.12.9Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.9
v0.12.8Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.8
v0.12.7Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.7
v0.12.6Compare Source
See: https://github.com/astral-sh/uv/releases/tag/0.12.6
biomejs/pre-commit
v2.6.8Compare Source
v2.6.7Compare Source
v2.6.6Compare Source
v2.6.5Compare Source
v2.6.4Compare Source
v2.6.3Compare Source
v2.6.2Compare Source
v2.6.1Compare Source
v2.6.0Compare Source
v2.5.15Compare Source
v2.5.14Compare Source
v2.5.13Compare Source
v2.5.12Compare Source
v2.5.11Compare Source
v2.5.10Compare Source
v2.5.9Compare Source
coveragepy/coveragepy (coverage)
v7.17.3Compare Source
Fix: using
patch = fork, a child process wasn't measured unlesspatch = subprocesswas also used, as described inissue 2340. This is now fixedin
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. Closesissue 2364_.Fix: with
patch = subprocesson Python 3.13, a measured subprocess thatwas 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: #2340
.. _pull 2342: #2342
.. _pull 2353: #2353
.. _issue 2364: #2364
.. _issue 2362: #2362
.. _pull 2371: #2371
.. _changes_7-17-2:
v7.17.2Compare Source
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 combinesautomatically) always failed.
coverage combineandcoverage debug datafailed when a data fileexisted 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.
.. _issue 2356: #2356
.. _changes_7-17-1:
v7.17.1Compare Source
Fix: a one-line class or function body immediately followed by another
statement (such as
class Foo: ...on its own line) was incorrectlyreported as a missing branch when using the sys.monitoring core. This is now
fixed, closing
issue 2167_ andissue 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 pagedeleted, but the pages next to it still linked to it. Now a page is also
rewritten when its neighbors change.
Fix:
--fail-undernow uses at least the decimal precision of thethreshold for both the comparison and failure message. With
precision=0,a total of 0.4 now passes
--fail-under=0.3and fails--fail-under=0.5with 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
&. Now they are properlyescaped only once.
Fix:
--source=/measured no files. A file system root can't be a sourcedirectory, 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.
.. _issue 2167: #2167
.. _issue 2291: #2291
.. _issue 2295: #2295
.. _issue 2337: #2337
.. _changes_7-17-0:
v7.17.0Compare Source
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
withstatements could make awithline 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:orwhile 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
elseandexceptclauses. 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 :ref:
error description <error_cant_combine>in the docs now lists common causes and how to find theprocess that wrote the file.
Fix: at coverage totals close to 0 or 100, the XML report could get incorrect
line-ratevalues like8.333e-05or1. This is now fixed, closingissue 2293_ andissue 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:
legal