Skip to content

Update all dependencies - #65

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

Update all dependencies#65
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all

Conversation

@renovate

@renovate renovate Bot commented Aug 11, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change Age Confidence
actions/checkout action major v4 → v7 age confidence
actions/download-artifact action major v4 → v8 age confidence
actions/setup-python action major v5 → v7 age confidence
actions/upload-artifact action major v4 → v7 age confidence
coverage dependencies minor 7.14.1 → 7.17.2 age confidence
kubernetes dependencies major 36.0.2 → 37.0.2 age confidence
pylint (changelog) dependencies major ^3.0.0 → ^4.0.0 age confidence
sphinxcontrib-apidoc dependencies minor ^0.5.0 → ^0.6.0 age confidence
ubuntu github-runner major 24.04 → 26.04 age confidence

Release Notes

actions/checkout

v7.0.1

Compare Source

v7.0.0

Compare Source

  • Block checking out fork PR for pull_request_target and workflow_run by @​aiqiaoy in #​2454
  • Various dependency updates

v6.1.0

Compare Source

What's Changed

https://github.blog/changelog/2026-06-18-safer-pull_request_target-defaults-for-github-actions-checkout/ for more details about this breaking change

Full Changelog: actions/checkout@v6.0.3...v6.1.0

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v5.1.0

Compare Source

What's Changed

https://github.blog/changelog/2026-06-18-safer-pull_request_target-defaults-for-github-actions-checkout/ for more details about this breaking change

Full Changelog: actions/checkout@v5.0.1...v5.1.0

v5.0.1

Compare Source

v5.0.0

Compare Source

actions/download-artifact

v8.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v8.0.1...v8.0.2

v8.0.1

Compare Source

What's Changed

Full Changelog: actions/download-artifact@v8...v8.0.1

v8.0.0

Compare Source

v8 - What's new

[!IMPORTANT]
actions/download-artifact@​v8 has been migrated to an ESM module. This should be transparent to the caller but forks might need to make significant changes.

[!IMPORTANT]
Hash mismatches will now error by default. Users can override this behavior with a setting change (see below).

Direct downloads

To support direct uploads in actions/upload-artifact, the action will no longer attempt to unzip all downloaded files. Instead, the action checks the Content-Type header ahead of unzipping and skips non-zipped files. Callers wishing to download a zipped file as-is can also set the new skip-decompress parameter to true.

Enforced checks (breaking)

A previous release introduced digest checks on the download. If a download hash didn't match the expected hash from the server, the action would log a warning. Callers can now configure the behavior on mismatch with the digest-mismatch parameter. To be secure by default, we are now defaulting the behavior to error which will fail the workflow run.

ESM

To support new versions of the @​actions/* packages, we've upgraded the package to ESM.

What's Changed

Full Changelog: actions/download-artifact@v7...v8.0.0

v7.0.0

Compare Source

v7 - What's new

[!IMPORTANT]
actions/download-artifact@​v7 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v6 had preliminary support for Node 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v6.0.0...v7.0.0

v6.0.0

Compare Source

What's Changed

BREAKING CHANGE: this update supports Node v24.x. This is not a breaking change per-se but we're treating it as such.

New Contributors

Full Changelog: actions/download-artifact@v5...v6.0.0

v5.0.0

Compare Source

What's Changed
v5.0.0
🚨 Breaking Change

This release fixes an inconsistency in path behavior for single artifact downloads by ID. If you're downloading single artifacts by ID, the output path may change.

What Changed

Previously, single artifact downloads behaved differently depending on how you specified the artifact:

  • By name: name: my-artifact → extracted to path/ (direct)
  • By ID: artifact-ids: 12345 → extracted to path/my-artifact/ (nested)

Now both methods are consistent:

  • By name: name: my-artifact → extracted to path/ (unchanged)
  • By ID: artifact-ids: 12345 → extracted to path/ (fixed - now direct)
Migration Guide
✅ No Action Needed If:
  • You download artifacts by name
  • You download multiple artifacts by ID
  • You already use merge-multiple: true as a workaround
⚠️ Action Required If:

You download single artifacts by ID and your workflows expect the nested directory structure.

Before v5 (nested structure):

- uses: actions/download-artifact@v4
  with:
    artifact-ids: 12345
    path: dist

# Files were in: dist/my-artifact/

Where my-artifact is the name of the artifact you previously uploaded

To maintain old behavior (if needed):

- uses: actions/download-artifact@v5
  with:
    artifact-ids: 12345
    path: dist/my-artifact  # Explicitly specify the nested path
New Contributors

Full Changelog: actions/download-artifact@v4...v5.0.0

actions/setup-python

v7.1.0

Compare Source

What's Changed
Enhancements
Dependency Upgrade
New Contributors

Full Changelog: actions/setup-python@v7.0.0...v7.1.0

v7.0.0

Compare Source

What's Changed
Enhancements
Bug Fix
Dependency Upgrade
New Contributors

Full Changelog: actions/setup-python@v6...v7.0.0

v6.3.0

Compare Source

What's Changed
Enhancement
Dependency update
Documentation
New Contributors

Full Changelog: actions/setup-python@v6.2.0...v6.3.0

v6.2.0

Compare Source

What's Changed

Dependency Upgrades

Full Changelog: actions/setup-python@v6...v6.2.0

v6.1.0

Compare Source

What's Changed

Enhancements:
Dependency and Documentation updates:

New Contributors

Full Changelog: actions/setup-python@v6...v6.1.0

v6.0.0

Compare Source

What's Changed

Breaking Changes

Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. See Release Notes

Enhancements:
Bug fixes:
Dependency updates:

New Contributors

Full Changelog: actions/setup-python@v5...v6.0.0

actions/upload-artifact

v7.0.2

Compare Source

What's Changed

  • Improves artifact download retries when the service returns HTTP 429 (rate limiting), including honoring valid Retry-After headers.
  • Updates @​actions/artifact to v6.3.1.

New Contributors

Full Changelog: actions/upload-artifact@v7.0.1...v7.0.2

v7.0.1

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v7...v7.0.1

v7.0.0

Compare Source

v7 What's new

Direct Uploads

Adds support for uploading single files directly (unzipped). Callers can set the new archive parameter to false to skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. The name parameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.

ESM

To support new versions of the @actions/* packages, we've upgraded the package to ESM.

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v6...v7.0.0

v6.0.0

Compare Source

v6 - What's new

[!IMPORTANT]
actions/upload-artifact@​v6 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v5 had preliminary support for Node.js 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed

Full Changelog: actions/upload-artifact@v5.0.0...v6.0.0

v5.0.0

Compare Source

What's Changed

BREAKING CHANGE: this update supports Node v24.x. This is not a breaking change per-se but we're treating it as such.

New Contributors

Full Changelog: actions/upload-artifact@v4...v5.0.0

coveragepy/coveragepy (coverage)

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 in POSIX paths but unsafe in reports: in XML 1.0 they make the
      document non-well-formed, and in a terminal they act as escape sequences
      (colors, title/clipboard sequences, cursor moves that forge output). Now
      the XML report, the text and Markdown summary reports, and coverage debug data replace non-printable characters in names. Printable names are
      unchanged.

    • A file pattern (from include, omit, or a [paths] alias)
      containing a newline sent the glob-to-regex translation into an infinite
      loop, hanging the process. Newlines in patterns are now handled like any
      other character.

  • Fixes in the implementation of the C tracer:

    • If a plugin's dynamic_source_filename method raised an exception, lines
      in that function could be recorded as belonging to a different file. Also
      fixed some minor memory leaks in the C tracer.

    • The refcount of None was mismanaged during function calls, including
      comprehensions. This was unlikely to cause an actual problem, but is now
      fixed. Thanks, Andrew Dalke.

    • The C tracer held borrowed references to dictionary values, which was
      unsafe on free-threaded Python. Now it takes its own references.

    • An internal error while recording a new file could be reported as a
      confusing SystemError instead of the actual exception.

  • Performance: the text summary report (coverage report) held on to every
    file's parsed source until it finished, so its memory use grew with the size
    of the project: ten times or more what 7.14 used on large projects. Now it
    keeps only what it needs to print. Fixes issue 2277_.

  • Performance: HTML reports should be about 5% faster to produce.

  • Kept the political banner in the README. Closes issue 2344_.

.. _issue 1987: #​1987
.. _issue 2277: #​2277
.. _issue 2293: #​2293
.. _issue 2294: #​2294
.. _issue 2314: #​2314
.. _issue 2335: #​2335
.. _issue 2338: #​2338
.. _issue 2344: #​2344

.. _changes_7-16-2:

[v7.16.2](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Ver

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

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from 496ca9c to 8eba457 Compare October 15, 2025 17:52
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 1ecf877 to 23fcabe Compare October 24, 2025 21:55
@renovate
renovate Bot force-pushed the renovate/all branch 4 times, most recently from f3242b5 to aaae1a3 Compare November 13, 2025 20:44
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 2f44e26 to 019c492 Compare November 20, 2025 17:56
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 390516c to 0d2d39f Compare December 12, 2025 21:34
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 1cae755 to 5284c15 Compare February 9, 2026 13:42
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from cc75f9e to eb6ff6d Compare February 26, 2026 20:52
@renovate
renovate Bot force-pushed the renovate/all branch from f9f76b2 to 505afa6 Compare May 10, 2026 21:11
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from f03525e to ce46521 Compare May 26, 2026 22:04
@renovate
renovate Bot force-pushed the renovate/all branch from ce46521 to a30dcae Compare June 1, 2026 23:02
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 066f259 to 25db451 Compare June 14, 2026 16:58
@renovate
renovate Bot force-pushed the renovate/all branch from 7f30793 to 30df0e9 Compare July 5, 2026 13:44
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from 302410f to e8d6f65 Compare August 12, 2026 03:11
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 30ae90d to 380759e Compare September 18, 2026 21:14
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from fcf0faa to e670cb3 Compare October 1, 2026 04:16
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 215a683 to 15df73e Compare October 13, 2026 00:45
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 09f5ddf to fcde5ef Compare October 23, 2026 14:07
@renovate
Update all dependencies
2d834d6 
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants