Skip to content

chore(deps): update all dependencies - #809

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all

Conversation

@renovate

@renovate renovate Bot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
ansible-builder 3.1.1 → 3.2.0 age confidence dependency-groups minor
ansible-builder 3.1.1 → 3.2.0 age confidence project.dependencies minor
ansible-compat (changelog) 26.9.0 → 26.11.0 age confidence project.dependencies minor
ansible-creator (changelog) 26.9.0 → 26.11.0 age confidence project.dependencies minor
ansible-dev-environment (changelog) 26.9.0 → 26.11.0 age confidence project.dependencies minor
ansible-lint (changelog) 26.9.0 → 26.11.0 age confidence project.dependencies minor
ansible-navigator (changelog) 26.9.0 → 26.11.0 age confidence project.dependencies minor
astral-sh/uv-pre-commit 0.12.5 → 0.13.9 age confidence repository minor
biomejs/pre-commit v2.5.8 → v2.6.8 age confidence repository minor
coverage 7.16.1 → 7.17.3 age confidence dependency-groups minor 7.17.4
django (changelog) 5.2.17 → 5.2.19 age confidence project.optional-dependencies patch
django-stubs (changelog) 6.1.1 → 6.1.2 age confidence dependency-groups patch
gunicorn (changelog) 26.2.0 → 27.0.1 age confidence project.optional-dependencies major
jsh9/pydoclint 0.9.1 → 0.12.0 age confidence repository minor
kubernetes ==36.0.3 → ==37.0.2 age confidence major 37.0.3
molecule (changelog) 26.9.0 → 26.11.0 age confidence project.dependencies minor
molecule-plugins (changelog) ==26.7.15 → ==26.11.0 age confidence minor
mypy (changelog) 2.3.1 → 2.4.1 age confidence dependency-groups minor
pip (changelog) 26.2.1 → 26.3 age confidence dependency-groups minor
pipx (changelog) 1.17.6 → 1.18.19 age confidence dependency-groups minor
prek (source, changelog) 0.5.3 → 0.5.11 age confidence dependency-groups patch
pydoclint 0.9.1 → 0.12.0 age confidence dependency-groups minor
pylint (changelog) 4.0.9 → 4.1.4 age confidence dependency-groups minor
pytest (changelog) 9.1.1 → 9.2.0 age confidence project.optional-dependencies minor
pytest (changelog) 9.1.1 → 9.2.0 age confidence dependency-groups minor
pytest-ansible (changelog) 26.9.0 → 26.11.0 age confidence project.dependencies minor
python 3.14 → 3.15 age confidence uses-with minor
ruff (source, changelog) 0.16.9 → 0.17.6 age confidence dependency-groups minor
tombi 1.5.5 → 1.11.3 age confidence dependency-groups minor
tox (changelog) 4.64.2 → 4.67.15 age confidence dependency-groups minor
tox-ansible (changelog) 26.9.0 → 26.11.0 age confidence project.dependencies minor
tox-uv (changelog) 1.36.0 → 1.37.9 age confidence dependency-groups minor
types-pyyaml (changelog) 6.0.12.20260906 → 6.0.12.20261113 age confidence dependency-groups patch 6.0.12.20261122
types-requests (changelog) 2.33.0.20260906 → 2.33.0.20261030 age confidence dependency-groups patch
ubuntu 24.04 → 26.04 age confidence github-runner major

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

ansible/ansible-builder (ansible-builder)

v3.2.0

Compare Source

What's Changed

  • Support for Python 3.15.
  • Dropped support for Python 3.9 and 3.10. Python 3.11 is now the minimum.
  • Ability to disable colorized output.
  • Symlink preservation with additional_build_files file copies.
  • Ability to detect parse errors from the most recent versions of bindep.
  • Deprecation of versions 1 and 2 of the execution environment YAML file format.

See the porting guide for version 3.2 for more details.

ansible/ansible-compat (ansible-compat)

v26.11.0

Compare Source

What's Changed

Full Changelog: ansible/ansible-compat@v26.10.0...v26.11.0

v26.10.0

Compare Source

What's Changed

Full Changelog: ansible/ansible-compat@v26.9.0...v26.10.0

ansible/ansible-creator (ansible-creator)

v26.11.0

Compare Source

What's Changed

Full Changelog: ansible/ansible-creator@v26.10.0...v26.11.0

v26.10.0

Compare Source

What's Changed

Full Changelog: ansible/ansible-creator@v26.9.0...v26.10.0

ansible/ansible-dev-environment (ansible-dev-environment)

v26.11.0

Compare Source

What's Changed

Full Changelog: ansible/ansible-dev-environment@v26.10.0...v26.11.0

v26.10.0

Compare Source

What's Changed

Full Changelog: ansible/ansible-dev-environment@v26.9.0...v26.10.0

ansible/ansible-lint (ansible-lint)

v26.11.0

Compare Source

What's Changed

New Contributors

Full Changelog: ansible/ansible-lint@v26.10.1...v26.11.0

v26.10.1

Compare Source

What's Changed

Full Changelog: ansible/ansible-lint@v26.10.0...v26.10.1

v26.10.0

Compare Source

What's Changed

New Contributors

Full Changelog: ansible/ansible-lint@v26.9.0...v26.10.0

ansible/ansible-navigator (ansible-navigator)

v26.11.0

Compare Source

What's Changed

New Contributors

Full Changelog: ansible/ansible-navigator@v26.10.0...v26.11.0

v26.10.0

Compare Source

What's Changed

New Contributors

Full Changelog: ansible/ansible-navigator@v26.8.0...v26.10.0

astral-sh/uv-pre-commit

v0.13.9

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.13.9

v0.13.8

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.13.8

v0.13.7

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.13.7

v0.13.6

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.13.6

v0.13.5

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.13.5

v0.13.4

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.13.4

v0.13.3

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.13.3

v0.13.2

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.13.2

v0.13.1

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.13.1

v0.13.0

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.13.0

v0.12.24

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.24

v0.12.23

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.23

v0.12.22

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.22

v0.12.21

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.21

v0.12.20

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.20

v0.12.19

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.19

v0.12.18

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.18

v0.12.17

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.17

v0.12.16

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.16

v0.12.15

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.15

v0.12.14

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.14

v0.12.13

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.13

v0.12.12

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.12

v0.12.11

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.11

v0.12.10

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.10

v0.12.9

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.9

v0.12.8

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.8

v0.12.7

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.7

v0.12.6

Compare Source

See: https://github.com/astral-sh/uv/releases/tag/0.12.6

biomejs/pre-commit

v2.6.8

Compare Source

v2.6.7

Compare Source

v2.6.6

Compare Source

v2.6.5

Compare Source

v2.6.4

Compare Source

v2.6.3

Compare Source

v2.6.2

Compare Source

v2.6.1

Compare Source

v2.6.0

Compare Source

v2.5.15

Compare Source

v2.5.14

Compare Source

v2.5.13

Compare Source

v2.5.12

Compare Source

v2.5.11

Compare Source

v2.5.10

Compare Source

v2.5.9

Compare Source

coveragepy/coveragepy (coverage)

v7.17.3

Compare Source

  • Fix: using patch = fork, a child process wasn't measured unless patch = subprocess was also used, as described in issue 2340. This is now fixed
    in 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. Closes issue 2364_.

  • Fix: with patch = subprocess on Python 3.13, a measured subprocess that
    was 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.2

Compare 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 combines
      automatically) always failed.

    • coverage combine and coverage debug data failed when a data file
      existed 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.1

Compare Source

  • Fix: a one-line class or function body immediately followed by another
    statement (such as class Foo: ... on its own line) was incorrectly
    reported as a missing branch when using the sys.monitoring core. This is now
    fixed, closing issue 2167_ and issue 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 page
    deleted, but the pages next to it still linked to it. Now a page is also
    rewritten when its neighbors change.

  • Fix: --fail-under now uses at least the decimal precision of the
    threshold for both the comparison and failure message. With precision=0,
    a total of 0.4 now passes --fail-under=0.3 and fails --fail-under=0.5
    with 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 &amp;. Now they are properly
    escaped only once.

  • Fix: --source=/ measured no files. A file system root can't be a source
    directory, 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.0

Compare 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 with statements could make a with
    line 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: or
    while 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
    else and except clauses. 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 the
    process that wrote the file.

  • Fix: at coverage totals close to 0 or 100, the XML report could get incorrect
    line-rate values like 8.333e-05 or 1. This is now fixed, closing
    issue 2293_ and issue 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:

    • File names (and plugin names) can contain control characters, which are
      legal

[!IMPORTANT]
✂ PR body was truncated to here.

@coderabbitai

coderabbitai Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

Note

Reviews paused

It 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 reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

No actionable comments were generated in the recent review.

Walkthrough

The pre-commit configuration updates the pinned revisions for uv-pre-commit, Biome, and pydoclint. The devspace requirements update the pinned version of molecule-plugins[podman].

Changes: Pinned dependency updates

Layer / File(s) Summary
Update pinned versions
.pre-commit-config.yaml, devspaces/context/requirements.txt
Updates uv-pre-commit from 0.12.5 to 0.12.21, Biome from v2.5.8 to v2.5.14, pydoclint from 0.9.1 to 0.10.1, and molecule-plugins[podman] from 26.7.15 to 26.9.28.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: ssbarnea

Merge Risk: Minimal · previous review c2e5c

No actionable issue is established for these dependency updates; the PR is mergeable after normal checks.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

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

📥 Commits

Reviewing files that changed from the base of the PR and between b74c1a7 and c2e5c2a.

⛔ 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.

@renovate
renovate Bot force-pushed the renovate/all branch 14 times, most recently from c021384 to 37ab0af Compare October 5, 2026 22:02
@renovate
renovate Bot force-pushed the renovate/all branch 10 times, most recently from de0d64e to 938209b Compare October 11, 2026 01:12
@renovate
renovate Bot force-pushed the renovate/all branch 13 times, most recently from 2902d62 to def67e5 Compare October 22, 2026 22:30
@renovate
renovate Bot force-pushed the renovate/all branch 15 times, most recently from 4f88692 to 9a0179c Compare October 28, 2026 22:29
@renovate

renovate Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pyproject.toml
Artifact update for coverage resolved to version 7.17.4, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 7.17.3
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

0 participants