You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note the astrix (*) at the end. That was always added by default in the previous version. And is the default for pattern. But if you specify your own pattern and it used be a prefix, you MUST add the astrix (*) at the end. It's not suffixed by default anymore because we want to give you full controll over the pattern (after refs/tags/) so you can do things like semver (v*[0-9].*[0-9].*[0-9]) with it without us meddling with it.
To support direct uploads in actions/upload-artifact, the action will no longer attempt to unzip all downloaded files. Instead, the action checks the Content-Type header ahead of unzipping and skips non-zipped files. Callers wishing to download a zipped file as-is can also set the new skip-decompress parameter to false.
Enforced checks (breaking)
A previous release introduced digest checks on the download. If a download hash didn't match the expected hash from the server, the action would log a warning. Callers can now configure the behavior on mismatch with the digest-mismatch parameter. To be secure by default, we are now defaulting the behavior to error which will fail the workflow run.
ESM
To support new versions of the @actions/* packages, we've upgraded the package to ESM.
[!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
Update GHES guidance to include reference to Node 20 version by @patrikpolyak in #440
BREAKING fix: inconsistent path behavior for single artifact downloads by ID by @GrantBirki in #416
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@v4with:
artifact-ids: 12345path: dist### Files were in: dist/my-artifact/
Where my-artifact is the name of the artifact you previously uploaded
Enhance caching in setup-node with automatic package manager detection by @priya-kinthali in #1348
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
Adds support for uploading single files directly (unzipped). Callers can set the new archive parameter to false to skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. The name parameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.
ESM
To support new versions of the @actions/* packages, we've upgraded the package to ESM.
All future releases are also immutable, if you want to know more about what this means checkout the docs.
This release also has two breaking changes
New format for manifest-file
The previously deprecated way of defining a custom version manifest to control which uv versions are available and where to download them from got removed. The functionality is still there but you have to use the new format.
No more major and minor tags
To increase security even more we will stop publishing minor tags. You won't be able to use @v8 or @v8.0 any longer. We do this because pinning to major releases opens up users to supply chain attacks like what happened to tj-actions.
[!TIP]
Use the immutable tag as a version astral-sh/setup-uv@v8.0.0
Or even better the githash astral-sh/setup-uv@cec208311dfd045dd5311c1add060b2062131d57
We now default to download uv from releases.astral.sh.
This means by default we don't hit the GitHub API at all and shouldn't see any rate limits and timeouts any more.
🚀 Enhancements
Fetch uv from Astral's mirror by default @zsol (#809)
🧰 Maintenance
Switch to ESM for source and test, use CommonJS for dist @eifinger (#806)
This release addresses a long-standing source of timeouts and rate-limit failures in setup-uv.
Previously, the action resolved version identifiers like 0.5.x by iterating over available uv releases via the GitHub API to find the best match. In contrast, latest and exact versions such as 0.5.0 skipped version resolution entirely and downloaded uv directly.
The manifest-file input was an earlier attempt to improve this. It allows providing an url to a file that lists available versions, checksums, and even custom download URLs. The action also shipped with such a manifest.
However, because that bundled file could become outdated whenever new uv releases were published, the action still had to fall back to the GitHub API in many cases.
This release solves the problem by sourcing version data from Astral’s versions repository via the raw content endpoint:
By using the raw endpoint instead of the GitHub API, version resolution no longer depends on API authentication and is much less likely to run into rate limits or timeouts.
[!TIP]
The next section is only interesting for users of the manifest-file input
The manifest-file input lets you override that source with your own URL, for example to test custom uv builds or alternate download locations.
The manifest file must be in NDJSON format, where each line is a JSON object representing a version and its artifacts. For example:
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Oct 6, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Oct 7, 2024
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Oct 7, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Oct 8, 2024
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Oct 9, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Oct 14, 2024
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Oct 14, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Oct 26, 2024
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Nov 6, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Nov 6, 2024
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Nov 7, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Nov 8, 2024
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Nov 8, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Nov 9, 2024
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Nov 11, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Nov 11, 2024
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Nov 15, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Nov 17, 2024
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Nov 19, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Nov 19, 2024
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Nov 20, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Nov 23, 2024
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Nov 25, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Nov 25, 2024
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Nov 27, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Nov 28, 2024
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Nov 29, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Nov 29, 2024
renovatebot
changed the title
Update peter-evans/create-pull-request action to v7
chore(deps): update peter-evans/create-pull-request action to v7
Nov 30, 2024
renovatebot
changed the title
chore(deps): update peter-evans/create-pull-request action to v7
Update peter-evans/create-pull-request action to v7
Nov 30, 2024
renovatebot
changed the title
chore(deps): update github-actions (major)
Update github-actions (major)
Mar 23, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.11.1→^3.0.0^6.0.1→^9.0.0^22.15.29→^24.0.0v1.4.0→v2.0.0v4.3.0→v5.0.4v4.3.1→v6.0.2v5.0.1→v6.0.2v4.3.0→v8.0.1v7.1.0→v8.0.0v4.4.0→v6.3.0v4.6.2→v7.0.0v4→v7v7.3.0→v8.0.0v6.3.0→v7.0.0v3.0.2→v4.0.120→2416→24v4.0.0→v5.0.0v6.1.0→v8.1.0v3.0.0→v4.0.1v5.2.0→v7.1.0^5.8.3→^6.0.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
actions/toolkit (@actions/core)
v3.0.0import()instead ofrequire()v2.0.3@actions/http-clientto3.0.2v2.0.1v2.0.0actions/toolkit (@actions/github)
v9.1.0actions_orchestration_idto user-agent when theACTIONS_ORCHESTRATION_IDenvironment variable is set #2364v9.0.0import()instead ofrequire()const { getOctokit, context } = await import('@​actions/github')@octokit/core/typesv8.0.1undicito6.23.0@actions/http-clientto3.0.2v8.0.0@octokit/core^7.0.6@octokit/plugin-paginate-rest^14.0.0@octokit/plugin-rest-endpoint-methods^17.0.0@octokit/request^10.0.7@octokit/request-error^7.1.0v7.0.0@actions/http-clientWyriHaximus/github-action-get-previous-tag (WyriHaximus/github-action-get-previous-tag)
v2.0.0Compare Source
Migration
Migrating from
prefixtopatterngoing from this:To:
Note the astrix (
*) at the end. That was always added by default in the previous version. And is the default forpattern. But if you specify your own pattern and it used be a prefix, you MUST add the astrix (*) at the end. It's not suffixed by default anymore because we want to give you full controll over the pattern (afterrefs/tags/) so you can do things like semver (v*[0-9].*[0-9].*[0-9]) with it without us meddling with it.v2.0.0
Bug 🐞
Dependencies 📦
Feature 🏗
Enhancement ✨
prefixintopatternthanks to @WyriHaximusactions/cache (actions/cache)
v5.0.4Compare Source
v5.0.3Compare Source
What's Changed
@actions/cacheto v5.0.5 (Resolves: https://github.com/actions/cache/security/dependabot/33)@actions/coreto v2.0.3Full Changelog: actions/cache@v5...v5.0.3
v5.0.2Compare Source
v5.0.1Compare Source
v5.0.0Compare Source
actions/checkout (actions/checkout)
v6.0.2Compare Source
v6.0.1Compare Source
v6.0.0Compare Source
v5.0.1Compare Source
What's Changed
Full Changelog: actions/checkout@v5...v5.0.1
v5.0.0Compare Source
What's Changed
v2.327.1
Release Notes
Make sure your runner is updated to this version or newer to use this release.
Full Changelog: actions/checkout@v4...v5.0.0
actions/download-artifact (actions/download-artifact)
v8.0.1Compare Source
What's Changed
Full Changelog: actions/download-artifact@v8...v8.0.1
v8.0.0Compare Source
v8 - What's new
Direct downloads
To support direct uploads in
actions/upload-artifact, the action will no longer attempt to unzip all downloaded files. Instead, the action checks theContent-Typeheader ahead of unzipping and skips non-zipped files. Callers wishing to download a zipped file as-is can also set the newskip-decompressparameter tofalse.Enforced checks (breaking)
A previous release introduced digest checks on the download. If a download hash didn't match the expected hash from the server, the action would log a warning. Callers can now configure the behavior on mismatch with the
digest-mismatchparameter. To be secure by default, we are now defaulting the behavior toerrorwhich will fail the workflow run.ESM
To support new versions of the @actions/* packages, we've upgraded the package to ESM.
What's Changed
errorby @danwkennedy in #461Full Changelog: actions/download-artifact@v7...v8.0.0
v7.0.0Compare Source
v7 - What's new
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.0Compare 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.@actions/artifacttov4.0.0v6.0.0by @danwkennedy in #438New Contributors
Full Changelog: actions/download-artifact@v5...v6.0.0
v5.0.0Compare 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:
name: my-artifact→ extracted topath/(direct)artifact-ids: 12345→ extracted topath/my-artifact/(nested)Now both methods are consistent:
name: my-artifact→ extracted topath/(unchanged)artifact-ids: 12345→ extracted topath/(fixed - now direct)Migration Guide
✅ No Action Needed If:
merge-multiple: trueas a workaroundYou download single artifacts by ID and your workflows expect the nested directory structure.
Before v5 (nested structure):
To maintain old behavior (if needed):
New Contributors
Full Changelog: actions/download-artifact@v4...v5.0.0
actions/github-script (actions/github-script)
v8.0.0Compare Source
actions/setup-node (actions/setup-node)
v6.3.0Compare Source
What's Changed
Enhancements:
devEnginesfield by @susnux in #1283Dependency updates:
Bug fixes:
New Contributors
Full Changelog: actions/setup-node@v6...v6.3.0
v6.2.0Compare Source
v6.1.0Compare Source
What's Changed
Enhancement:
Dependency updates:
Documentation update:
Full Changelog: actions/setup-node@v6...v6.1.0
v6.0.0Compare Source
What's Changed
Breaking Changes
Dependency Upgrades
Full Changelog: actions/setup-node@v5...v6.0.0
v5.0.0Compare Source
What's Changed
Breaking Changes
This update, introduces automatic caching when a valid
packageManagerfield is present in yourpackage.json. This aims to improve workflow performance and make dependency management more seamless.To disable this automatic caching, set
package-manager-cache: falseMake 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
actions/upload-artifact (actions/upload-artifact)
v7.0.0Compare Source
v7 What's new
Direct Uploads
Adds support for uploading single files directly (unzipped). Callers can set the new
archiveparameter tofalseto skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. Thenameparameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.ESM
To support new versions of the
@actions/*packages, we've upgraded the package to ESM.What's Changed
New Contributors
Full Changelog: actions/upload-artifact@v6...v7.0.0
v6.0.0Compare Source
v5.0.0Compare Source
astral-sh/setup-uv (astral-sh/setup-uv)
v8.0.0: 🌈 Immutable releases and secure tagsCompare Source
This is the first immutable release of
setup-uv🥳All future releases are also immutable, if you want to know more about what this means checkout the docs.
This release also has two breaking changes
New format for
manifest-fileThe previously deprecated way of defining a custom version manifest to control which
uvversions are available and where to download them from got removed. The functionality is still there but you have to use the new format.No more major and minor tags
To increase security even more we will stop publishing minor tags. You won't be able to use
@v8or@v8.0any longer. We do this because pinning to major releases opens up users to supply chain attacks like what happened to tj-actions.🚨 Breaking changes
🧰 Maintenance
v7.6.0: 🌈 Fetch uv from Astral's mirror by defaultCompare Source
Changes
We now default to download uv from
releases.astral.sh.This means by default we don't hit the GitHub API at all and shouldn't see any rate limits and timeouts any more.
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
v7.5.0: 🌈 Useastral-sh/versionsas version providerCompare Source
No more rate-limits
This release addresses a long-standing source of timeouts and rate-limit failures in setup-uv.
Previously, the action resolved version identifiers like 0.5.x by iterating over available uv releases via the GitHub API to find the best match. In contrast, latest and exact versions such as 0.5.0 skipped version resolution entirely and downloaded uv directly.
The
manifest-fileinput was an earlier attempt to improve this. It allows providing an url to a file that lists available versions, checksums, and even custom download URLs. The action also shipped with such a manifest.However, because that bundled file could become outdated whenever new uv releases were published, the action still had to fall back to the GitHub API in many cases.
This release solves the problem by sourcing version data from Astral’s versions repository via the raw content endpoint:
https://raw.githubusercontent.com/astral-sh/versions/refs/heads/main/v1/uv.ndjson
By using the raw endpoint instead of the GitHub API, version resolution no longer depends on API authentication and is much less likely to run into rate limits or timeouts.
The
manifest-fileinput lets you override that source with your own URL, for example to test custom uv builds or alternate download locations.The manifest file must be in NDJSON format, where each line is a JSON object representing a version and its artifacts. For example:
{"version":"0.10.7","artifacts":[{"platform":"x86_64-unknown-linux-gnu","variant":"default","url":"https://example.com/uv-x86_64-unknown-linux-gnu.tar.gz","archive_format":"tar.gz","sha256":"..."}]} {"version":"0.10.6","artifacts":[{"platform":"x86_64-unknown-linux-gnu","variant":"default","url":"https://example.com/uv-x86_64-unknown-linux-gnu.tar.gz","archive_format":"tar.gz","sha256":"..."}]}Changes
🚀 Enhancements
📚 Documentation
v7.4.0: 🌈 Add riscv64 architecture support to platform detectionCompare Source
Changes
Thank you @luhenry for adding support for riscv64 arch
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
v7.3.1: 🌈 fall back to VERSION_CODENAME when VERSION_ID is not availableCompare Source
Changes
This release adds support for running in containers like
debian:testingordebian:unstable🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates
crazy-max/ghaction-import-gpg (crazy-max/ghaction-import-gpg)
v7.0.0Compare Source
Full Changelog: crazy-max/ghaction-import-gpg@v6.3.0...v7.0.0
dorny/paths-filter (dorny/paths-filter)
v4.0.1Compare Source
What's Changed
New Contributors
Full Changelog: dorny/paths-filter@v4.0.0...v4.0.1
v4.0.0Compare Source
v3.0.3Compare Source
actions/node-versions (node)
v24.14.1: 24.14.1Compare Source
Node.js 24.14.1
v24.14.0: 24.14.0Compare Source
Node.js 24.14.0
v24.13.1: 24.13.1Compare Source
Node.js 24.13.1
v24.13.0: 24.13.0Compare Source
Node.js 24.13.0
v24.12.0: 24.12.0Compare Source
Node.js 24.12.0
v24.11.1: 24.11.1Compare Source
Node.js 24.11.1
v24.11.0: 24.11.0Compare Source
Node.js 24.11.0
v24.10.0: 24.10.0Compare Source
Node.js 24.10.0
v24.9.0: 24.9.0Compare Source
Node.js 24.9.0
v24.8.0: 24.8.0Compare Source
Node.js 24.8.0
v24.7.0: 24.7.0Compare Source
Node.js 24.7.0
v24.6.0: 24.6.0Compare Source
Node.js 24.6.0
v24.5.0: 24.5.0Compare Source
Node.js 24.5.0
v24.4.1: 24.4.1Compare Source
Node.js 24.4.1
v24.4.0: 24.4.0Compare Source
Node.js 24.4.0
v24.3.0: 24.3.0Compare Source
Node.js 24.3.0
v24.2.0: 24.2.0Compare Source
Node.js 24.2.0
v24.1.0: 24.1.0Compare Source
Node.js 24.1.0
v24.0.2: 24.0.2Compare Source
Node.js 24.0.2
v24.0.1: 24.0.1Compare Source
Node.js 24.0.1
v24.0.0: 24.0.0Compare Source
Node.js 24.0.0
v22.22.2: 22.22.2Compare Source
Node.js 22.22.2
v22.22.1: 22.22.1Compare Source
Node.js 22.22.1
v22.22.0: 22.22.0[Compare Source](https://re
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 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.
This PR was generated by Mend Renovate. View the repository job log.