build(deps): bump the all-dependencies group with 2 updates

[dependabot]

Bumps the all-dependencies group with 2 updates: astral-sh/setup-uv and MishaKav/pytest-coverage-comment.

Updates astral-sh/setup-uv from 7.4.0 to 7.6.0

Release notes

Sourced from astral-sh/setup-uv's releases.

v7.6.0 🌈 Fetch uv from Astral's mirror by default

Changes

We now default to download uv from releases.astral.sh. This means by default we don't hit the GitHub API at all and shouldn't see any rate limits and timeouts any more.

🚀 Enhancements

• Fetch uv from Astral's mirror by default @​zsol (#809)

🧰 Maintenance

• Switch to ESM for source and test, use CommonJS for dist @​eifinger (#806)
• chore: update known checksums for 0.10.10 @github-actions[bot] (#804)

⬆️ Dependency updates

• chore(deps): bump zizmorcore/zizmor-action from 0.5.0 to 0.5.2 @dependabot[bot] (#808)
• Bump deps @​eifinger (#805)

v7.5.0 🌈 Use astral-sh/versions as version provider

No more rate-limits

This release addresses a long-standing source of timeouts and rate-limit failures in setup-uv.

Previously, the action resolved version identifiers like 0.5.x by iterating over available uv releases via the GitHub API to find the best match. In contrast, latest and exact versions such as 0.5.0 skipped version resolution entirely and downloaded uv directly.

The manifest-file input was an earlier attempt to improve this. It allows providing an url to a file that lists available versions, checksums, and even custom download URLs. The action also shipped with such a manifest. However, because that bundled file could become outdated whenever new uv releases were published, the action still had to fall back to the GitHub API in many cases.

This release solves the problem by sourcing version data from Astral’s versions repository via the raw content endpoint:

https://raw.githubusercontent.com/astral-sh/versions/refs/heads/main/v1/uv.ndjson

By using the raw endpoint instead of the GitHub API, version resolution no longer depends on API authentication and is much less likely to run into rate limits or timeouts.

---

[!TIP] The next section is only interesting for users of the manifest-file input

The manifest-file input lets you override that source with your own URL, for example to test custom uv builds or alternate download locations.

The manifest file must be in NDJSON format, where each line is a JSON object representing a version and its artifacts. For example:

{"version":"0.10.7","artifacts":[{"platform":"x86_64-unknown-linux-gnu","variant":"default","url":"https://example.com/uv-x86_64-unknown-linux-gnu.tar.gz","archive_format":"tar.gz","sha256":"..."}]}
{"version":"0.10.6","artifacts":[{"platform":"x86_64-unknown-linux-gnu","variant":"default","url":"https://example.com/uv-x86_64-unknown-linux-gnu.tar.gz","archive_format":"tar.gz","sha256":"..."}]}

... (truncated)

Commits

• 37802ad Fetch uv from Astral's mirror by default (#809)
• 9f00d18 chore(deps): bump zizmorcore/zizmor-action from 0.5.0 to 0.5.2 (#808)
• fd8f376 Switch to ESM for source and test, use CommonJS for dist (#806)
• f9070de Bump deps (#805)
• cadb67b chore: update known checksums for 0.10.10 (#804)
• e06108d Use astral-sh/versions as primary version provider (#802)
• 0f6ec07 docs: replace copilot instructions with AGENTS.md (#794)
• 821e5c9 docs: add cross-client dependabot rollup skill (#793)
• See full diff in compare view

Updates MishaKav/pytest-coverage-comment from 1.6.0 to 1.7.1

Release notes

Sourced from MishaKav/pytest-coverage-comment's releases.

v1.7.1

What's Changed

• fix 5 security vulnerabilities in undici (6.23.0 → 6.24.1) (#260)
• bump dev dependencies

Full Changelog: MishaKav/pytest-coverage-comment@v1.7.0...v1.7.1

v1.7.0

What's Changed

• enable immutable releases for supply chain security (#256)
• bump flatted from 3.3.3 to 3.4.1 to fix security vulnerability

Note: No changes to action inputs, outputs, or behavior. This improves release security following GitHub's immutable releases feature.

Full Changelog: MishaKav/pytest-coverage-comment@v1.6.0...v1.7.0

Changelog

Sourced from MishaKav/pytest-coverage-comment's changelog.

Changelog of the Pytest Coverage Comment

Pytest Coverage Comment 1.7.1

Release Date: 2026-03-14

Changes

• fix 5 security vulnerabilities in undici (6.23.0 → 6.24.1) (#260)
• bump dev dependencies

Pytest Coverage Comment 1.7.0

Release Date: 2026-03-13

Changes

• enable immutable releases for supply chain security (#256)
• bump flatted from 3.3.3 to 3.4.1 to fix security vulnerability

Note: No changes to action inputs, outputs, or behavior. This improves release security following GitHub's immutable releases feature.

Pytest Coverage Comment 1.6.0

Release Date: 2026-03-06

Changes

• migrate codebase from JavaScript to TypeScript
• add unit tests (91 tests) using Vitest with V8 coverage

Note: This is an internal rewrite — no changes to action inputs, outputs, or behavior. Fully backward compatible.

Pytest Coverage Comment 1.5.0

Release Date: 2026-02-28

Changes

• feat: add hide-emoji option to hide emoji shortcodes from the test summary table (#251)
• docs: update README examples to use @v1 tag and latest action versions (checkout@v6, setup-python@v6)

Pytest Coverage Comment 1.4.0

Release Date: 2026-02-22

Changes

• feat: auto-detect and display branch coverage columns (Branch, BrPart) in coverage table (#110)
• supported for both text format (pytest --cov --cov-branch) and XML format (coverage.xml)

... (truncated)

Commits

• 2872928 Remove publish-immutable-actions workflow, bump deps, fix vulnerabilities (#2...
• 6b219ea Enable immutable releases for supply chain security (#256) (#258)
• 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 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

[github-actions]

Coverage Report •

File	Stmts	Miss	Branch	BrPart	Cover	Missing
TOTAL	37858	1732	3700	770	95%

report-only-changed-files is enabled. No files were changed during this commit :)

Tests	Skipped	Failures	Errors	Time
1268	0 💤	0 ❌	0 🔥	10m 8s ⏱️