chore(deps): bump astral-sh/setup-uv from 8.2.0 to 10.0.1

[dependabot]

Bumps astral-sh/setup-uv from 8.2.0 to 10.0.1.

Release notes

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

v10.0.1 🌈 Tolerate transient manifest timeouts

Changes

Thank you @​arguile- for making this action more resilient.

🐛 Bug fixes

• Tolerate transient manifest timeouts @​arguile- (#1016)

🧰 Maintenance

• chore: update known checksums for 0.12.4 @github-actions[bot] (#1017)

📚 Documentation

• docs: update version references to v10.0.0 @github-actions[bot] (#1014)

v10.0.0 🌈 Disable automatic caching for sensitive events and new QOL features

Changes

Another breaking release, directly after v9.0.0 but we think the added security justifies that.

Extra security by default

If you use the default enable-cache: auto this will now DISABLE THE CACHE to protect against cache poisoning for the following events:

• pull_request_target
• workflow_run
• release

You can read the full reasoning in astral-sh/setup-uv#984

version: latest-known

- name: Install the latest version of uv known to setup-uv
  uses: astral-sh/setup-uv@v10.0.0
  with:
    version: "latest-known"

This will now install the latest version with a checksum that is known by this action. The known uv checksums are automatically updated but will take a release of this action to take effect. You won't be always using the latest & greatest but you will have an extra level of security.

Read python version from .tool-versions

- name: Install uv based on the version defined in .tool-versions and also set python
  uses: astral-sh/setup-uv@v10.0.0
  with:
    version-file: "pyproject.toml"
</tr></table> 

... (truncated)

Commits

• 20cfd1b chore: update known checksums for 0.12.4 (#1017)
• d73a0ca Tolerate transient manifest timeouts (#1016)
• ae3b92d docs: update version references to v10.0.0 (#1014)
• ae62891 chore(deps): roll up Dependabot updates (#1013)
• f9cdb47 Reject paths in .tool-versions (#1007)
• 4f6036f Require pull requests for Dependabot rollups (#1005)
• 8d6402c chore(deps): roll up Dependabot updates (#1004)
• 46f427b Read Python version from .tool-versions (#996)
• 8ed89c5 ci: pin Alpine container image (#995)
• 8473c7f chore(deps): roll up Dependabot updates (#994)
• Additional commits viewable 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by CodeRabbit

• Chores
  • Updated the tooling used by the project’s code-check, documentation publishing, and package release workflows.
  • The change applies to automation only; no user-facing functionality or workflow steps changed.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 79bcf226-2faa-4913-b7e4-1b0f5f422f62

📥 Commits

Reviewing files that changed from the base of the PR and between 4922d4b and 92fab3c.

📒 Files selected for processing (3)

• .github/workflows/code-check.yml
• .github/workflows/release_docs.yml
• .github/workflows/release_pypi.yml

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review.

---

📝 Walkthrough

Walkthrough

Three GitHub Actions workflows update their pinned astral-sh/setup-uv action from v8.2.0 to v10.0.1. The workflows’ other configuration remains unchanged.

Changes

Workflow action updates

Layer / File(s)	Summary
Update workflow action pins .github/workflows/code-check.yml, .github/workflows/release_docs.yml, .github/workflows/release_pypi.yml	All three workflows now use astral-sh/setup-uv v10.0.1 instead of v8.2.0.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~5 minutes

Change: Other

Suggested reviewers: danfimov

Merge Risk: ⚪ Minimal · up to 92fab

The workflows update setup-uv to v10.0.1 without other configuration changes. No actionable merge-blocking issue is established; merge after normal workflow checks pass.

Security Architecture Review

Security architecture risk: 🔵 Low · up to 92fab

The documentation workflow retains its existing main-branch trigger and deployment permissions. No introduced vulnerability is established, but cache isolation and recovery behavior across the major action upgrade remain unverified.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

• inferred — If an attacker could influence restored dependencies, their execution would occur in the documentation deployment job and could affect the published site. The evidence does not establish that cache influence is attainable or define exposure beyond this workflow.

Security Findings and Attack Paths

• observed — No Security finding is retained. The cache-related candidate remains deferred: workflow triggers are now established, but attacker reachability, cross-version cache isolation, and introduced or worsened exposure remain unresolved.

Trust Boundaries and Controls

• inferred — The unchanged push-to-main trigger is counterevidence against this PR introducing direct untrusted pull-request execution in the documentation job. It does not prove cache isolation from other producers or establish branch-protection guarantees.

Resilience and Maintainability Implications

• observed — The workflow does not define explicit cache cleanup, concurrency control, or deployment rollback. This configuration is unchanged; action-managed cache ownership, terminal states, and recovery under failure, interruption, repetition, or concurrency remain unverified rather than established defects.

🚥 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 and concisely describes the main change: updating astral-sh/setup-uv from version 8.2.0 to version 10.0.1.
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

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

_{Comment @coderabbitai help to get the list of available commands.}