chore(deps): update actions/setup-python action to v7

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/setup-python	action	major	v6 → v7

---

Release Notes

actions/setup-python (actions/setup-python)

v7.0.0

Compare Source

v7

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[claude]

LGTM — straightforward CI dependency bump.

What was reviewed: the three workflow files updating actions/setup-python from v6 to v7.0.0 (test, docs, and publish pipelines). Checked that the version bump is applied consistently across all matrix jobs and doesn't touch any credentials, permissions, or publish logic.

Extended reasoning...

Overview

This PR is an automated Renovate dependency update bumping actions/setup-python from v6 to v7.0.0 across three GitHub Actions workflow files: python-tests.yml, publish-docs.yaml, and publish-to-test-pypi.yml. No other logic, permissions, or code was changed — this is a pure action-version pin update.

Security risks

None. The change only bumps a pinned major version of a widely-used, trusted GitHub Action (actions/setup-python). It does not touch secrets, permissions, publish/auth steps (PyPI trusted publishing via OIDC remains untouched), or any application code.

Level of scrutiny

Low. This is a mechanical, single-purpose dependency bump with no behavioral ambiguity — the same action is used in the same way in each workflow, just at a newer version. CI itself will validate that the new action version works correctly across the Python version matrix (3.10–3.14) before merge.

Other factors

The bug hunting system found no bugs. Two candidate issues about inconsistent version-pinning style (full semver v7.0.0 vs major-only v6/v7) were raised and correctly ruled out as non-issues — this is simply how Renovate pins major-version bumps by default, and it's consistent with the existing style already used elsewhere in these same files (e.g. actions/checkout@v7, actions/upload-artifact@v7).

[claude]

LGTM — straightforward CI dependency bump.

Extended reasoning...

Overview

This PR is an automated Renovate update bumping the actions/setup-python GitHub Action from v6 to v7 across three workflow files: publish-docs.yaml, publish-to-test-pypi.yml, and python-tests.yml. Each change is a single-line version bump with no other configuration modified.

Security risks

None. This only affects the pinned version of a widely-used, official GitHub Action used to set up Python in CI. It does not touch application code, secrets handling, or permissions in the workflows.

Level of scrutiny

Minimal scrutiny is appropriate here — this is a mechanical dependency bump with no logic changes, consistent with the low-risk profile of routine CI action updates. The three edits are identical in nature (same action, same version change) and don't interact with each other.

Other factors

No bugs were found by the bug hunting system, and there is no prior review history on this PR to reconcile. The workflows continue to reference actions/setup-python with the same with: parameters (python-version), so behavior should be unaffected beyond whatever v7 changes internally (a major version bump, but for a setup action this risk is low and would surface immediately in CI on the next run).