Skip to content

chore(deps): update github actions (feature/geti-inspect) #3163

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
oep-renovate wants to merge 1 commit into
base: feature/geti-inspect
Choose a base branch
from
Open

chore(deps): update github actions (feature/geti-inspect) #3163

oep-renovate wants to merge 1 commit into from

Conversation

@oep-renovate
Copy link
Contributor

@oep-renovate oep-renovate bot commented Dec 1, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
actions/cache action major v4 -> v5
actions/checkout action major v5.0.0 -> v6.0.1
actions/checkout action major v5 -> v6
actions/checkout action major v4.1.2 -> v6.0.1
actions/checkout action major v4.2.2 -> v6.0.1
actions/create-github-app-token action minor v2.1.4 -> v2.2.1
actions/download-artifact action major v4.3.0 -> v7.0.0
actions/download-artifact action major v5 -> v7
actions/setup-node action major v4.0.2 -> v6.1.0
actions/setup-python action digest e797f83 -> 83679a8
actions/setup-python action major v5.6.0 -> v6.1.0
actions/setup-python action minor v6.0.0 -> v6.1.0
actions/stale action digest 5f858e3 -> 9971854
actions/upload-artifact action major v4.6.2 -> v6.0.0
actions/upload-artifact action major v4.3.1 -> v6.0.0
actions/upload-artifact action major v4 -> v6
astral-sh/setup-uv action major v6.2.1 -> v7.1.5
astral-sh/setup-uv action major v6.8.0 -> v7.1.5
astral-sh/uv uses-with minor 0.8.8 -> 0.9.17
github/codeql-action action major v3.30.6 -> v4.31.8
j178/prek-action action digest ef075ff -> 91fd7d7
open-edge-platform/geti-ci action digest 4ec90fb -> 4768cec
peter-evans/create-pull-request action major v7.0.8 -> v8.0.0
renovatebot/github-action action major v43.0.15 -> v44.1.0
softprops/action-gh-release action minor v2.3.4 -> v2.5.0
step-security/harden-runner action minor v2.13.1 -> v2.14.0
tj-actions/changed-files action patch v47.0.0 -> v47.0.1

Release Notes

actions/cache (actions/cache)

v5

Compare Source

actions/checkout (actions/checkout)

v6.0.1

Compare Source

What's Changed

Full Changelog: actions/checkout@v6...v6.0.1

v6.0.0

Compare Source

v5.0.1

Compare Source

actions/create-github-app-token (actions/create-github-app-token)

v2.2.1

Compare Source

Bug Fixes
  • deps: bump the production-dependencies group with 2 updates (#​311) (b212e6a)

v2.2.0

Compare Source

Bug Fixes
Features
actions/download-artifact (actions/download-artifact)

v7.0.0

Compare Source

v7 - What's new

[!IMPORTANT]
actions/download-artifact@​v7 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v6 had preliminary support for Node 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed
New Contributors

Full Changelog: actions/download-artifact@v6.0.0...v7.0.0

v6.0.0

Compare Source

What's Changed

BREAKING CHANGE: this update supports Node v24.x. This is not a breaking change per-se but we're treating it as such.

New Contributors

Full Changelog: actions/download-artifact@v5...v6.0.0

v5.0.0

Compare Source

What's Changed
v5.0.0
🚨 Breaking Change

This release fixes an inconsistency in path behavior for single artifact downloads by ID. If you're downloading single artifacts by ID, the output path may change.

What Changed

Previously, single artifact downloads behaved differently depending on how you specified the artifact:

  • By name: name: my-artifact → extracted to path/ (direct)
  • By ID: artifact-ids: 12345 → extracted to path/my-artifact/ (nested)

Now both methods are consistent:

  • By name: name: my-artifact → extracted to path/ (unchanged)
  • By ID: artifact-ids: 12345 → extracted to path/ (fixed - now direct)
Migration Guide
✅ No Action Needed If:
  • You download artifacts by name
  • You download multiple artifacts by ID
  • You already use merge-multiple: true as a workaround
⚠️ Action Required If:

You download single artifacts by ID and your workflows expect the nested directory structure.

Before v5 (nested structure):

- uses: actions/download-artifact@v4
  with:
    artifact-ids: 12345
    path: dist

# Files were in: dist/my-artifact/

Where my-artifact is the name of the artifact you previously uploaded

To maintain old behavior (if needed):

- uses: actions/download-artifact@v5
  with:
    artifact-ids: 12345
    path: dist/my-artifact  # Explicitly specify the nested path
New Contributors

Full Changelog: actions/download-artifact@v4...v5.0.0

actions/setup-node (actions/setup-node)

v6.1.0

Compare Source

What's Changed
Enhancement:
Dependency updates:
Documentation update:

Full Changelog: actions/setup-node@v6...v6.1.0

v6.0.0

Compare Source

What's Changed

Breaking Changes

Dependency Upgrades

Full Changelog: actions/setup-node@v5...v6.0.0

v5.0.0

Compare Source

What's Changed
Breaking Changes

This update, introduces automatic caching when a valid packageManager field is present in your package.json. This aims to improve workflow performance and make dependency management more seamless.
To disable this automatic caching, set package-manager-cache: false

steps:
- uses: actions/checkout@v5
- uses: actions/setup-node@v5
  with:
    package-manager-cache: false

Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. See Release Notes

Dependency Upgrades
New Contributors

Full Changelog: actions/setup-node@v4...v5.0.0

v4.4.0

Compare Source

What's Changed
Bug fixes:
Enhancement:
Dependency update:
New Contributors

Full Changelog: actions/setup-node@v4...v4.4.0

v4.3.0

Compare Source

What's Changed
Dependency updates
New Contributors

Full Changelog: actions/setup-node@v4...v4.3.0

v4.2.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/setup-node@v4...v4.2.0

v4.1.0

Compare Source

What's Changed
  • Resolve High Security Alerts by upgrading Dependencies by @​aparnajyothi-y in #​1132
  • Upgrade IA Publish by @​Jcambass in #​1134
  • Revise isGhes logic by @​jww3 in #​1148
  • Add architecture to cache key by @​pengx17 in #​843
    This addresses issues with caching by adding the architecture (arch) to the cache key, ensuring that cache keys are accurate to prevent conflicts.
    Note: This change may break previous cache keys as they will no longer be compatible with the new format.
New Contributors

Full Changelog: actions/setup-node@v4...v4.1.0

v4.0.4

Compare Source

What's Changed
Documentation changes:
New Contributors

Full Changelog: actions/setup-node@v4...v4.0.4

v4.0.3

Compare Source

What's Changed
Bug fixes:
Documentation changes:
Dependency updates:
New Contributors

Full Changelog: actions/setup-node@v4...v4.0.3

actions/setup-python (actions/setup-python)

v6.1.0

Compare Source

What's Changed

Enhancements:
Dependency and Documentation updates:

New Contributors

Full Changelog: actions/setup-python@v6...v6.1.0

v6.0.0

Compare Source

What's Changed
Breaking Changes

Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. See Release Notes

Enhancements:
Bug fixes:
Dependency updates:
New Contributors

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

actions/upload-artifact (actions/upload-artifact)

v6.0.0

Compare Source

v6 - What's new

[!IMPORTANT]
actions/upload-artifact@​v6 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v5 had preliminary support for Node.js 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed

Full Changelog: actions/upload-artifact@v5.0.0...v6.0.0

v5.0.0

Compare Source

What's Changed

BREAKING CHANGE: this update supports Node v24.x. This is not a breaking change per-se but we're treating it as such.

New Contributors

Full Changelog: actions/upload-artifact@v4...v5.0.0

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

v7.1.5: 🌈 allow setting cache-local-path without enable-cache: true

Compare Source

Changes

#​612 fixed a faulty behavior where this action set UV_CACHE_DIR even though enable-cache was false. It also fixed the cases were the cache dir is already configured in a settings file like pyproject.toml or UV_CACHE_DIR was already set. Here the action shouldn't overwrite or set UV_CACHE_DIR.

These fixes introduced an unwanted behavior: You can still set cache-local-path but this action didn't do anything. This release fixes that.

You can now use cache-local-path to automatically set UV_CACHE_DIR even when enable-cache is false (or gets set to false by default e.g. on self-hosted runners)

- name: This is now possible
  uses: astral-sh/setup-uv@v7
  with:
    enable-cache: false
    cache-local-path: "/path/to/cache"
🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates

v7.1.4: 🌈 Fix libuv closing bug on Windows

Compare Source

Changes

This release fixes the bug Assertion failed: !(handle->flags & UV_HANDLE_CLOSING) on Windows runners

🐛 Bug fixes
🧰 Maintenance

v7.1.3: 🌈 Support act

Compare Source

Changes

This bug fix release adds support for https://github.com/nektos/act
It was previously broken because of a too new undici version and TS transpilation target.

Compatibility with act is now automatically tested.

🐛 Bug fixes
🧰 Maintenance
📚 Documentation

v7.1.2: 🌈 Speed up extraction on Windows

Compare Source

Changes

@​lazka fixed a bug that caused extracting uv to take up to 30s. Thank you!

🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates

v7.1.1: 🌈 Fix empty workdir detection and lowest resolution strategy

Compare Source

Changes

This release fixes a bug where the working-directory input was not used to detect an empty work dir. It also fixes the lowest resolution strategy resolving to latest when only a lower bound was specified.

Special thanks to @​tpgillam for the first contribution!

🐛 Bug fixes
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

v7.1.0: 🌈 Support all the use cases

Compare Source

Changes

Support all the use cases!!!
... well, that we know of.

This release adds support for some use cases that most users don't encounter but are useful for e.g. people running Gitea.

The input resolution-strategy lets you use the lowest possible version of uv from a version range. Useful if you want to test your tool with different versions of uv.

If you use activate-environment the path to the activated venv is now also exposed under the output venv.

Downloaded python installations can now also be uploaded to the GitHub Actions cache backend. Useful if you are running in act and have configured your own backend and don't want to download python again, and again over a slow internet connection.

Finally the path to installed python interpreters is now added to the PATH on Windows.

🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

v7.0.0: 🌈 node24 and a lot of bugfixes

Compare Source

Changes

This release comes with a load of bug fixes and a speed up. Because of switching from node20 to node24 it is also a breaking change. If you are running on GitHub hosted runners this will just work, if you are using self-hosted runners make sure, that your runners are up to date. If you followed the normal installation instructions your self-hosted runner will keep itself updated.

This release also removes the deprecated input server-url which was used to download uv releases from a different server.
The manifest-file input supersedes that functionality by adding a flexible way to define available versions and where they should be downloaded from.

Fixes
  • The action now respects when the environment variable UV_CACHE_DIR is already set and does not overwrite it. It now also finds cache-dir settings in config files if you set them.
  • Some users encountered problems that cache pruning took forever because they had some uv processes running in the background. Starting with uv version 0.8.24 this action uses uv cache prune --ci --force to ignore the running processes
  • If you just want to install uv but not have it available in path, this action now respects UV_NO_MODIFY_PATH
  • Some other actions also set the env var UV_CACHE_DIR. This action can now deal with that but as this could lead to unwanted behavior in some edgecases a warning is now displayed.
Improvements

If you are using minimum version specifiers for the version of uv to install for example

[tool.uv]
required-version = ">=0.8.17"

This action now detects that and directly uses the latest version. Previously it would download all available releases from the uv repo
to determine the highest matching candidate for the version specifier, which took much more time.

If you are using other specifiers like 0.8.x this action still needs to download all available releases because the specifier defines an upper bound (not 0.9.0 or later) and "latest" would possibly not satisfy that.

🚨 Breaking changes
🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates

v6.8.0: 🌈 Add **/*.py.lock to cache-dependency-glob

Compare Source

Changes

Thanks to @​parched the default cache-dependency-glob now also find all lock files generated by uv lock --script

🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

v6.7.0: 🌈 New inputs restore-cache and save-cache

[Compare Source](https://redirect.github.com/a

@oep-renovate oep-renovate bot force-pushed the renovate/feature/geti-inspect-github-actions branch 2 times, most recently from d612a2a to 891ff6b Compare December 3, 2025 02:41
@codecov-commenter
Copy link

codecov-commenter commented Dec 3, 2025

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@oep-renovate oep-renovate bot force-pushed the renovate/feature/geti-inspect-github-actions branch 6 times, most recently from d26a035 to d4c992d Compare December 10, 2025 02:43
@oep-renovate oep-renovate bot force-pushed the renovate/feature/geti-inspect-github-actions branch from d4c992d to d067a31 Compare December 12, 2025 02:43
@oep-renovate oep-renovate bot requested a review from ivanzati as a code owner December 12, 2025 02:43
@oep-renovate
chore(deps): update github actions
26ec3d2 
Signed-off-by: oep-renovate[bot] <212772560+oep-renovate[bot]@users.noreply.github.com>
@oep-renovate oep-renovate bot force-pushed the renovate/feature/geti-inspect-github-actions branch from d067a31 to 26ec3d2 Compare December 13, 2025 02:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mramotowski mramotowski Awaiting requested review from mramotowski mramotowski is a code owner

@AlexanderBarabanov AlexanderBarabanov Awaiting requested review from AlexanderBarabanov AlexanderBarabanov is a code owner

@ashwinvaidya17 ashwinvaidya17 Awaiting requested review from ashwinvaidya17 ashwinvaidya17 is a code owner

@ivanzati ivanzati Awaiting requested review from ivanzati ivanzati is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@codecov-commenter