Upgrade astral-sh/setup-uv to 10.3.2 with a passing CI run #409

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Overview

Dependabot PR #405 bumped astral-sh/setup-uv from 10.3.0 to 10.3.2 and was closed unmerged because CI never passed on it. The upgrade has no breaking changes, but re-running failed jobs on it cannot work: they fail at Download wheel artifact before any test runs, because the wheel artifact they need has expired.

Complexity: Low
Target branch: release-v0.9.x

Context

• On Bump astral-sh/setup-uv from 10.3.0 to 10.3.2 #405, the re-run of Python unit tests + cryptography (3.11) failed with:

  Artifact not found for name: wheel
  

• The build job uploads wheel with retention-days: 1 (tox.yml:54); every test job downloads it.
• Re-running only failed jobs more than a day after the original run reuses the expired artifact instead of rebuilding it.
• 10.3.1 fixes the Failed to save: Unable to reserve cache warning on concurrent cache uploads; 10.3.2 adds uv 0.13.5 checksums.

The Change

• All 12 astral-sh/setup-uv pins should move to 10.3.2 together, in tox.yml, check-docs.yml, pre-commit.yml and python-publish.yml.
• The test jobs in tox.yml should run and pass against 10.3.2.
• Re-running failed test jobs after the wheel artifact expires should not fail at Download wheel artifact.

Acceptance Criteria

• No workflow pins astral-sh/setup-uv at any version other than 10.3.2.
• One tox.yml run on the upgrade PR, with every matrix job of Python unit tests and Python unit tests + cryptography executed, passes.
• Re-running a failed tox.yml test job more than a day after its run reaches the test step.

AI usage

Claude Code reviewed #405's changelog, diff and CI logs and drafted this issue; rtibblesbot's review on #405 recommended closing it in favour of this issue.

Filed from #405's review.