[rhoai-3.3] Update github-actions

[konflux-internal-p02]

This PR contains the following updates:

Package	Type	Update	Change	Pending
actions/checkout	action	patch	v7.0.0 → v7.0.1
astral-sh/uv	uses-with	patch	0.11.28 → 0.11.29	0.11.31 (+1)
github/codeql-action	action	patch	v4.37.0 → v4.37.1	v4.37.3 (+1)
jdx/mise-action	action	patch	v4.2.0 → v4.2.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

actions/checkout (actions/checkout)

v7.0.1

Compare Source

• Skip running unsafe pr check if input is default by @​aiqiaoy in #​2518
• Trim only ascii whitespace for branch by @​aiqiaoy in #​2521
• Escape values passed to --unset by @​aiqiaoy in #​2530
• Various dependency updates

astral-sh/uv (astral-sh/uv)

v0.11.29

Compare Source

Released on 2026-07-15.

Python

• Use gzip-compressed artifacts for PyPy downloads (#​20265)

Enhancements

• Add JSON output to uv tree (#​19978)
• Add CUDA 13.2 as a supported PyTorch backend (#​20267)
• Prefer local artifacts over URLs when installing from pylock.toml (#​20393)
• Clarify diagnostics for unsatisfiable direct requirement ranges (#​20227)
• Include the selected project name in missing-extra errors (#​20358)

Preview features

• Preserve extras and dependency-group conflict context when selecting locked project tools (#​20078)
• Split OSV audit queries that exceed the service's 1,000-package limit (#​20398)
• Apply OSV fixed-version information only to the matching package and ecosystem (#​20399)
• Skip the virtualenv distutils monkeypatch on Python 3.10 and later (#​20222)
• Report invalid uv audit --service-url values instead of panicking (#​20374)
• Include preview settings in the published SchemaStore schema (#​20304)

Performance

• Reduce resolver work by widening selected versions across ranges without other known candidates (#​20115)
• Defer client and build setup for no-op uv sync operations (#​20364)
• Reuse workspace discovery during frozen syncs (#​20363)
• Reuse workspace discovery after resolving settings (#​20356)
• Reuse workspace discovery in uv tree, uv export, uv format, and uv audit (#​20359)
• Avoid cache and interpreter setup when reading a project version (#​20360)

Bug fixes

• Reject duplicate active package entries in pylock.toml (#​20391)
• Preserve direct-archive hashes in uv pip freeze output (#​20395)
• Explain conflicting root requirements instead of displaying an empty version range (#​20228)
• Prevent build-backend data paths from escaping the project or bypassing wheel exclusions (#​20397)
• Reject PEP 517 backend paths outside the source tree, including paths that escape through symlinks (#​20387)
• Redact credentials from failed Git fetch commands (#​20401)
• Fix exclusive post-release range ordering to match PEP 440 (#​20268)
• Canonicalize equivalent PEP 440 ranges during dependency resolution (#​20182)
• Honor Python version pins when initializing scripts (#​20404)
• Respect package-scoped source filtering for scripts (#​20389)
• Report existing environment incompatibilities when uv pip install --strict has nothing to install (#​20388)
• Continue scanning platlib when purelib is missing (#​20405)
• Handle versionless .egg-info files as legacy package metadata (#​20403)
• Make repeated locking idempotent for impossible cross-variable platform markers (#​20369)
• Report invalid cloud credential endpoint URLs instead of panicking (#​20372)
• Report invalid pylock.toml artifact URLs instead of panicking (#​20373)
• Report non-UTF-8 virtual environment paths instead of panicking while generating activation scripts (#​20375)
• Return an unsupported-operation error from unimplemented build-backend requirement hooks (#​20376)

Documentation

• Clarify --no-build behavior for editable requirements (#​20234)
• Document uv's threat model (#​20236)
• Reduce the number of badges in the README (#​11257)

github/codeql-action (github/codeql-action)

v4.37.1

Compare Source

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #​3956
• Update default CodeQL bundle version to 2.26.1. #​4019

jdx/mise-action (jdx/mise-action)

v4.2.1: : Signed checksums and PATH export fix

Compare Source

A small patch release with two user-facing fixes: mise downloads are now verified against minisign-signed release checksums by default, and the env input no longer leaks the runner's PATH into subsequent steps.

Fixed

Verify mise downloads with signed checksums (#​548) by @​jdx

The action now embeds mise's minisign public key and verifies SHASUMS256.txt.minisig before trusting any release checksums, then checks the downloaded mise binary's SHA256 against the verified list. This applies to both GitHub release archives (verified before extraction) and the default mise.jdx.dev CDN path (verified against the signed checksum for the matching release asset). If a CDN download fails verification, the action warns and falls back to the signed GitHub release asset instead of installing an unverified binary.

• The existing sha256 input still works as an explicit override.
• Pinned mise versions older than 2024.12.24 (which predate minisign checksums) get a warning and skip signed verification rather than failing.
• Because tar installs now extract from a verified file on disk, the previous streaming download | tar fast path is replaced with a download-then-verify-then-extract flow.

Thanks to @​potiuk for the detailed threat-model writeup in #​547.

Exclude PATH from environment export (#​556) by @​jdx

The env input has always documented that "PATH modifications are not part of this", but since the switch to mise env --json in #​252 (needed for redaction support), the action was exporting every string value returned by mise — including the computed PATH — into GITHUB_ENV. That effectively snapshotted the runner's entire PATH into subsequent steps and let [env] _.path entries in mise.toml leak past the action's own PATH management.

exportMiseEnv now skips PATH (case-insensitive) when exporting JSON env vars, restoring the documented behavior. Normal mise env vars are still exported, and PATH continues to be managed by the action's own setup (e.g. add_shims_to_path). Fixes #​555.

Full Changelog: jdx/mise-action@v4.2.0...v4.2.1

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign ysok for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[konflux-internal-p02]

Caution

There are some errors in your PipelineRun template.

PipelineRun	Error
odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-v3-3-push.yaml	yaml validation error: line 77: did not find expected key

[openshift-ci]

Hi @konflux-internal-p02[bot]. Thanks for your PR.

I'm waiting for a red-hat-data-services 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.