Skip to content

NO-JIRA: ci(deps): bump actions/setup-python from 6.2.0 to 7.0.0 - #9089

Merged
openshift-merge-bot[bot] merged 1 commit into
mainfrom
dependabot/github_actions/actions/setup-python-7.0.0
Jul 27, 2026
Merged

NO-JIRA: ci(deps): bump actions/setup-python from 6.2.0 to 7.0.0#9089
openshift-merge-bot[bot] merged 1 commit into
mainfrom
dependabot/github_actions/actions/setup-python-7.0.0

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps actions/setup-python from 6.2.0 to 7.0.0.

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

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 documentation build environment to use a newer pinned Python setup action version.
    • Documentation build steps and behavior remain unchanged.

@dependabot dependabot Bot added area/ci-tooling Indicates the PR includes changes for CI or tooling ok-to-test Indicates a non-member PR verified by an org member that is safe to test. labels Jul 24, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

The reusable documentation workflow updates its pinned actions/setup-python reference from the commit associated with v6.2.0 to the commit associated with v7.0.0. Other workflow steps, inputs, permissions, and build commands remain unchanged.

Suggested reviewers: enxebre, jparrill

🚥 Pre-merge checks | ✅ 11
✅ Passed checks (11 passed)
Check name Status Explanation
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.
Stable And Deterministic Test Names ✅ Passed This PR only bumps a workflow action pin in .github/workflows/docs-build-reusable.yaml; no test files or Ginkgo titles are added or modified.
Test Structure And Quality ✅ Passed Only .github/workflows/docs-build-reusable.yaml changed; no Ginkgo test code was modified, so the test-quality check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed Only a docs workflow Action pin changed; no manifests, controllers, or scheduling constraints were introduced.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Only a docs workflow action pin changed; no Ginkgo e2e tests or IPv4/public-network assumptions were added.
No-Weak-Crypto ✅ Passed The PR only bumps actions/setup-python in a workflow; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons appear in the diff.
Container-Privileges ✅ Passed Only the setup-python SHA changed in a docs workflow; no container/K8s manifest or privileged securityContext settings were added.
No-Sensitive-Data-In-Logs ✅ Passed Only change is pinning actions/setup-python from v6.2.0 to v7.0.0; no log lines or secrets/PII exposures were added.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and accurately summarizes the main change: upgrading actions/setup-python from 6.2.0 to 7.0.0.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dependabot/github_actions/actions/setup-python-7.0.0

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

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/docs-build-reusable.yaml:
- Around line 18-21: Remove the unsupported pip-install input from the
actions/setup-python step and add a separate shell step running python -m pip
install -r docs/requirements.txt before the mkdocs build step in the workflow.
🪄 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 YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 04275200-df1b-4b1d-b82e-8c6278d47b4d

📥 Commits

Reviewing files that changed from the base of the PR and between 144cca9 and f71fd4b.

📒 Files selected for processing (1)
  • .github/workflows/docs-build-reusable.yaml

Comment on lines +18 to 21
- uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
with:
python-version: '3.x'
pip-install: '-r docs/requirements.txt'

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== workflow snippet =="
cat -n .github/workflows/docs-build-reusable.yaml | sed -n '1,80p'

echo
echo "== search for pip-install usage =="
rg -n "pip-install|setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97" .github/workflows . -g '!**/.git/**'

echo
echo "== pinned action metadata =="
python3 - <<'PY'
import urllib.request
url = "https://raw.githubusercontent.com/actions/setup-python/5fda3b95a4ea91299a34e894583c3862153e4b97/action.yml"
print(urllib.request.urlopen(url, timeout=20).read().decode())
PY

Repository: openshift/hypershift

Length of output: 4226


🏁 Script executed:

#!/bin/bash
set -euo pipefail

python3 - <<'PY'
import ssl, urllib.request
url = "https://raw.githubusercontent.com/actions/setup-python/5fda3b95a4ea91299a34e894583c3862153e4b97/action.yml"
ctx = ssl.create_default_context()
ctx.check_hostname = False
ctx.verify_mode = ssl.CERT_NONE
print(urllib.request.urlopen(url, context=ctx, timeout=20).read().decode())
PY

Repository: openshift/hypershift

Length of output: 2661


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== docs requirements =="
if [ -f docs/requirements.txt ]; then
  cat -n docs/requirements.txt
else
  echo "docs/requirements.txt not found"
fi

echo
echo "== docs workflow references =="
rg -n "mkdocs|pip install|requirements.txt|setup-python|pip-install|pip-version" .github/workflows docs -g '!**/.git/**'

echo
echo "== workflow files under docs build =="
git ls-files .github/workflows | sed -n '/docs/p'

Repository: openshift/hypershift

Length of output: 3399


Install docs dependencies explicitly

actions/setup-python does not accept pip-install, so line 21 is a no-op. Add a separate python -m pip install -r docs/requirements.txt step before mkdocs build.

🧰 Tools
🪛 zizmor (1.26.1)

[warning] 21-21: usage of GitHub Actions misfeatures (misfeature): installs packages in a brittle manner

(misfeature)

🤖 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/docs-build-reusable.yaml around lines 18 - 21, Remove the
unsupported pip-install input from the actions/setup-python step and add a
separate shell step running python -m pip install -r docs/requirements.txt
before the mkdocs build step in the workflow.

@openshift-ci
openshift-ci Bot requested review from enxebre and jparrill July 24, 2026 01:07
@openshift-ci

openshift-ci Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Bumps [actions/setup-python](https://github.com/actions/setup-python) from 6.2.0 to 7.0.0.
- [Release notes](https://github.com/actions/setup-python/releases)
-
[Commits](actions/setup-python@a309ff8...5fda3b9
7)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-version: 7.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
@github-actions
github-actions Bot force-pushed the dependabot/github_actions/actions/setup-python-7.0.0 branch from f71fd4b to 9c3cbe7 Compare July 24, 2026 01:10
@openshift-ci

openshift-ci Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

@dependabot[bot]: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@mgencur

mgencur commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

/retitle NO-JIRA: ci(deps): bump actions/setup-python from 6.2.0 to 7.0.0
/lgtm
/verified bypass

@openshift-ci openshift-ci Bot changed the title ci(deps): bump actions/setup-python from 6.2.0 to 7.0.0 NO-JIRA: ci(deps): bump actions/setup-python from 6.2.0 to 7.0.0 Jul 27, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. verified Signifies that the PR passed pre-merge verification criteria labels Jul 27, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@dependabot[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

Bumps actions/setup-python from 6.2.0 to 7.0.0.

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

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 documentation build environment to use a newer pinned Python setup action version.
  • Documentation build steps and behavior remain unchanged.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot

Copy link
Copy Markdown

@mgencur: The verified label has been added.

Details

In response to this:

/retitle NO-JIRA: ci(deps): bump actions/setup-python from 6.2.0 to 7.0.0
/lgtm
/verified bypass

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 27, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification

No second-stage tests were triggered for this PR.

This can happen when:

  • The changed files don't match any pipeline_run_if_changed patterns
  • All files match pipeline_skip_if_only_changed patterns
  • No pipeline-controlled jobs are defined for the main branch

Use /test ? to see all available tests.

@muraee

muraee commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

/approve

@openshift-ci

openshift-ci Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dependabot[bot], muraee

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 27, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit a9a864e into main Jul 27, 2026
5 checks passed
@dependabot
dependabot Bot deleted the dependabot/github_actions/actions/setup-python-7.0.0 branch July 27, 2026 13:57
mgencur added a commit to mgencur/hypershift that referenced this pull request Jul 28, 2026
actions/setup-python removed the pip-install input in v7.0.0 (it
installed into the global environment, conflicted with virtualenvs
and tools like uv, and wasn't picked up by Dependabot). Since this
workflow was already pinned to v7.0.0, its pip-install: '-r
docs/requirements.txt' input silently became a no-op, meaning docs
dependencies were never actually installed here.

Replace it with an explicit "pip install -r docs/requirements.txt"
step, matching the fix already proposed in openshift#9133.

Also watch docs-build-reusable.yaml in docs-build.yaml's paths
filter. That filter only watched docs/** and its own file, not the
reusable workflow it calls, which is how this exact breakage (from
PR openshift#9089's actions/setup-python bump) slipped through unnoticed: the
Docs Build check never ran on that PR since the file it changed
wasn't in the filter. Every other trigger/-reusable workflow pair in
this repo already references its reusable file in the paths filter;
this was an isolated gap specific to docs-build.yaml.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/ci-tooling Indicates the PR includes changes for CI or tooling jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants