Bump actions/setup-python from 3 to 7 - #80
Conversation
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 3 to 7. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@v3...v7) --- updated-dependencies: - dependency-name: actions/setup-python dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
WalkthroughThe release publishing workflow updates its Python setup step from ChangesRelease workflow
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 11✅ Passed checks (11 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/publish-release.yaml:
- Line 18: Update the actions/setup-python step in the publish workflow to
reference the action’s exact 40-character commit SHA instead of the mutable v7
tag, preserving the existing setup configuration.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: openshift-online/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 3beb7fcc-4368-4877-851c-3d846d39d007
📒 Files selected for processing (1)
.github/workflows/publish-release.yaml
|
|
||
| - name: Setup Python | ||
| uses: actions/setup-python@v3 | ||
| uses: actions/setup-python@v7 |
There was a problem hiding this comment.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '--- publish-release.yaml ---\n'
cat -n .github/workflows/publish-release.yaml | sed -n '1,80p'
printf '\n--- action pinning references in workflows ---\n'
rg -n "uses: .*`@v`[0-9]+|uses: .*@[0-9a-f]{7,40}" .github/workflows || trueRepository: openshift-online/ocm-support-cli
Length of output: 261
🌐 Web query:
actions/setup-python v7 release tag commit SHA GitHub
💡 Result:
As of July 20, 2026, a v7 release for actions/setup-python has not been officially released [1]. While recent development efforts have focused on migrating the action's internals to ECMAScript Modules (ESM) and upgrading dependencies [2][3], the latest available version listed in the official GitHub repository remains v6.3.0 [1][4]. Although some other GitHub Actions (such as actions/setup-node [5], actions/setup-go [6], and actions/upload-artifact [7]) have reached v7.0.0, the actions/setup-python repository has not yet tagged a v7 release [1]. The migration to ESM is currently being addressed in the codebase [2][3], and users should continue to use the v6 series (e.g., v6.3.0) for stable production workflows [1][4].
Citations:
- 1: https://github.com/actions/setup-python/releases
- 2: actions/setup-python@f8cf429
- 3: Migrate to ESM and upgrade dependencies actions/setup-python#1330
- 4: Update github-actions hugovk/tinytext#258
- 5: https://github.com/actions/setup-node/releases/tag/v7.0.0
- 6: https://github.com/actions/setup-go/releases/tag/v7.0.0
- 7: Bump the github-actions group across 1 directory with 10 updates nod-ai/amd-shark-ai#2887
🏁 Script executed:
#!/bin/bash
set -euo pipefail
sed -n '1,40p' .github/workflows/publish-release.yaml | cat -nRepository: openshift-online/ocm-support-cli
Length of output: 1199
Pin actions/setup-python to a full commit SHA. .github/workflows/publish-release.yaml:18
actions/setup-python@v7 is tag-pinned and should be replaced with the action’s 40-character commit SHA.
🧰 Tools
🪛 zizmor (1.26.1)
[error] 18-18: runtime artifacts potentially vulnerable to a cache poisoning attack (cache-poisoning): this step
(cache-poisoning)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.github/workflows/publish-release.yaml at line 18, Update the
actions/setup-python step in the publish workflow to reference the action’s
exact 40-character commit SHA instead of the mutable v7 tag, preserving the
existing setup configuration.
Source: Path instructions
Bumps actions/setup-python from 3 to 7.
Release notes
Sourced from actions/setup-python's releases.
... (truncated)
Commits
5fda3b9Pin SHA commits and update docs with latest versions (#1338)4ab7e95Merge pull request #1337 from actions/philip-gai/bump-actions-cache-6-2-00f3a009Remove the pip-install input (#1336)f8cf429Migrate to ESM and upgrade dependencies (#1330)54baeeaValidate and retry manifest fetch to prevent silent failures (#1332)c709277Annotation code fix (#1335)6849080remove EOL Python versions and Bumps numpy text fixture (#1333)0903b46Bump certifi from 2020.6.20 to 2024.7.4 in /tests/data (#1328)ece7cb0Fix pip cache error handling on Windows. (#1040)1d18d7aUpdate advanced-usage.md (#811)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)Summary by CodeRabbit