Skip to content

Bump actions/setup-python from 3 to 7 - #80

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/setup-python-7
Open

Bump actions/setup-python from 3 to 7#80
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/setup-python-7

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 20, 2026

Copy link
Copy Markdown

Bumps actions/setup-python from 3 to 7.

Release notes

Sourced from actions/setup-python's releases.

v7.0.0

What's Changed

Enhancements

Bug Fix

Dependency Upgrade

New Contributors

Full Changelog: actions/setup-python@v6...v7.0.0

v6.3.0

What's Changed

Enhancement

Dependency update

Documentation

New Contributors

Full Changelog: actions/setup-python@v6.2.0...v6.3.0

v6.2.0

What's Changed

Dependency Upgrades

... (truncated)

Commits

Dependabot compatibility score

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 release publishing workflow’s Python setup action to a newer version.
    • Release automation continues to run with the latest supported setup configuration.

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>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jul 20, 2026
@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

Walkthrough

The release publishing workflow updates its Python setup step from actions/setup-python@v3 to actions/setup-python@v7.

Changes

Release workflow

Layer / File(s) Summary
Update Python setup action
.github/workflows/publish-release.yaml
The “Setup Python” step now uses actions/setup-python@v7.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 11
✅ Passed checks (11 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the only substantive change: upgrading actions/setup-python from v3 to v7.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.
No-Weak-Crypto ✅ Passed Only change is actions/setup-python v3→v7 in a workflow; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons introduced.
Container-Privileges ✅ Passed PR only bumps actions/setup-python in a workflow; no privileged, hostPID/Network/IPC, SYS_ADMIN, root, or allowPrivilegeEscalation settings were added.
No-Sensitive-Data-In-Logs ✅ Passed The PR only bumps actions/setup-python to v7; no new logging or sensitive-data outputs were added.
No-Hardcoded-Secrets ✅ Passed Only change is bumping setup-python v3→v7; no hardcoded API keys, passwords, private keys, credentialed URLs, or secret-like literals were introduced.
No-Injection-Vectors ✅ Passed The PR only bumps actions/setup-python v3→v7 in a workflow; the diff adds no listed injection patterns.
Ai-Attribution ✅ Passed No AI-tool use is mentioned in the PR or commit; the only trailer is Signed-off-by, and no Assisted-by/Generated-by or Co-Authored-By markers appear.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dependabot/github_actions/actions/setup-python-7

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8232d5e and 1aebd11.

📒 Files selected for processing (1)
  • .github/workflows/publish-release.yaml


- name: Setup Python
uses: actions/setup-python@v3
uses: actions/setup-python@v7

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 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 || true

Repository: 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:


🏁 Script executed:

#!/bin/bash
set -euo pipefail

sed -n '1,40p' .github/workflows/publish-release.yaml | cat -n

Repository: 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants