chore(deps): bump actions/setup-python from 5 to 6#783
Conversation
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 5 to 6. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@v5...v6) --- updated-dependencies: - dependency-name: actions/setup-python dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
Dependencies
github_actions
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
Darktex
left a comment
Darktex
left a comment
There was a problem hiding this comment.
Note: This is an automated review by Claude Code, not a human review.
Alignment Review
Tier 1 — mechanical: PASS. Single-line bump of actions/setup-python@v5 → @v6 in .github/workflows/test.yml. YAML is well-formed; usage is just with: python-version: "3.11", which is unaffected by the v6 default changes, so no behavioral regression. This also brings test.yml in line with the other workflows in the repo that already pin setup-python@v6 (publish-pypi-core, deploy-hf-env, docs, manage-hf-collection).
Tier 2 — alignment: No concerns. CI dependency bump with no impact on OpenEnv invariants.
Approved.
Automated review by Claude Code | Learn more
Darktex
left a comment
Darktex
left a comment
There was a problem hiding this comment.
Note: This is an automated review by Claude Code, not a human review.
Tier 1 (correctness): One-line bump of actions/setup-python from v5 to v6 in test.yml. The only breaking change in v6 is a Node 24 runtime requirement (runner ≥ v2.327.1), which GitHub-hosted ubuntu-latest always satisfies. The python-version input is unchanged and fully supported; no cache inputs are used. This also brings test.yml in line with the other workflows that already use setup-python@v6.
Tier 2 (alignment): No new concerns. First-party actions are pinned to major-version tags repo-wide (a pre-existing pattern this PR is consistent with); a future move to SHA-pinning could be discussed separately but is out of scope here.
Verdict: approve.
Automated review by Claude Code | Learn more
Darktex
left a comment
Darktex
left a comment
There was a problem hiding this comment.
Note: This is an automated review by Claude Code, not a human review.
Alignment Review (automated)
Tier 1 (bugs/lint): None. Bumps actions/setup-python v5 -> v6 in test.yml. The only breaking change in v6 is the internal Node runtime moving to Node 24, which requires runner >= v2.327.1 — GitHub-hosted ubuntu-latest already satisfies this. The pinned python-version: "3.11" (and matrix "3.12") are unaffected; v6 did not change Python version resolution.
Tier 2 (alignment): None. Pure CI tooling bump with no effect on environment code, API boundaries, or any invariant.
Automated review by Claude Code | Learn more
Darktex
left a comment
Darktex
left a comment
There was a problem hiding this comment.
Note: This is an automated review by Claude Code, not a human review.
Tier 1 (correctness): Bumps actions/setup-python v5 → v6 in .github/workflows/test.yml. The edit is limited to the version tag; the python-version: "3.11" input is intact. This is a major version bump — v6 ships the Node 24 runtime and requires GitHub runner v2.327.1+.
I checked the other workflows: publish-pypi-core.yml, deploy-hf-env.yml, manage-hf-collection.yml, and docs.yml already reference actions/setup-python@v6, so this PR brings test.yml into line — after merge all usages are consistent at @v6.
Tier 2 (alignment): CI-only; no source/invariant impact. All affected jobs run on ubuntu-latest (which already satisfies the runner-version requirement); the one job on a larger runner (openspiel_base_build.yml) does not use setup-python, so the Node 24 requirement is moot there. Low risk.
Verdict: approve.
Automated review by Claude Code | Learn more
1 participant
Bumps actions/setup-python from 5 to 6.
Release notes
Sourced from actions/setup-python's releases.
... (truncated)
Commits
a309ff8Bump urllib3 from 2.6.0 to 2.6.3 in /tests/data (#1264)bfe8cc5Upgrade@actionsdependencies to Node 24 compatible versions (#1259)4f41a90Bump urllib3 from 2.5.0 to 2.6.0 in /tests/data (#1253)83679a8Bump@types/nodefrom 24.1.0 to 24.9.1 and update macos-13 to macos-15-intel ...bfc4944Bump prettier from 3.5.3 to 3.6.2 (#1234)97aeb3eBump requests from 2.32.2 to 2.32.4 in /tests/data (#1130)443da59Bump actions/publish-action from 0.3.0 to 0.4.0 & Documentation update for pi...cfd55cagraalpy: add graalpy early-access and windows builds (#880)bba65e5Bump typescript from 5.4.2 to 5.9.3 and update docs/advanced-usage.md (#1094)18566f8Improve wording and "fix example" (remove 3.13) on testing against pre-releas...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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)