[!IMPORTANT]
actions/download-artifact@v8 has been migrated to an ESM module. This should be transparent to the caller but forks might need to make significant changes.
[!IMPORTANT]
Hash mismatches will now error by default. Users can override this behavior with a setting change (see below).
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 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 true.
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
The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.
ℹ️ However, this is a major update that includes breaking changes. Artifacts created with versions v3 and below are not compatible with the v4 actions. Uploads and downloads must use the same major actions versions. There are also key differences from previous versions that may require updates to your workflows.
As well as the underlying npm package, @actions/artifact documentation.
Breaking Changes
download-artifact@v4+ is not currently supported on GitHub Enterprise Server (GHES) yet. If you are on GHES, you must use v3 (Node 16) or v3-node20 (Node 20).
On self hosted runners, additional firewall rules may be required.
Downloading artifacts that were created from action/upload-artifact@v3 and below are not supported.
For assistance with breaking changes, see MIGRATION.md.
Improvements
Downloads are significantly faster, upwards of 90% improvement in worst case scenarios.
Artifacts can be downloaded from other workflow runs and repositories when supplied with a PAT.
[!Important]
actions/download-artifact@v3.1.0 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.
This is a backport security updates release for GHES users. This version is deprecated on github.com and should not be used!
Node.js 24
This release updates the runtime to Node.js 24. The previous v3.0.2 ran on Node.js 16, which has reached end-of-life. Now this action will run on Node.js 24.
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.
[!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.
We will no longer include hidden files and folders by default in the upload-artifact action of this version. This reduces the risk that credentials are accidentally uploaded into artifacts. Customers who need to continue to upload these files can use a new option, include-hidden-files, to continue to do so.
The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.
ℹ️ However, this is a major update that includes breaking changes. Artifacts created with versions v3 and below are not compatible with the v4 actions. Uploads and downloads must use the same major actions versions. There are also key differences from previous versions that may require updates to your workflows.
[!Important]
actions/upload-artifact@v3.2.2 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.
This is a backport security updates release for GHES users. This version is deprecated on github.com and should not be used!
Node.js 24
This release updates the runtime to Node.js 24. The previous v3.2.1 ran on Node.js 16, which has reached end-of-life. Now this action will run on Node.js 24.
We will no longer include hidden files and folders by default in the upload-artifact action of this version. This reduces the risk that credentials are accidentally uploaded into artifacts. Customers who need to continue to upload these files can use a new option, include-hidden-files, to continue to do so.
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:
Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.
Release Notes
actions/download-artifact (actions/download-artifact)v8.0.1
Compare Source
What's Changed
Full Changelog: actions/download-artifact@v8...v8.0.1
v8.0.0
Compare 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 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 true.
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.
What's Changed
Full Changelog: actions/download-artifact@v7...v8.0.0
v8
Compare Source
v7.0.0
Compare 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
v7
Compare Source
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
v6
Compare Source
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:
Now both methods are consistent:
Migration Guide
✅ No Action Needed If:
⚠️ Action Required If:
You 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
v5
Compare Source
v4.3.0
Compare Source
What's Changed
New Contributors
Full Changelog: actions/download-artifact@v4.2.1...v4.3.0
v4.2.1
Compare Source
What's Changed
Full Changelog: actions/download-artifact@v4.2.0...v4.2.1
v4.2.0
Compare Source
What's Changed
New Contributors
Full Changelog: actions/download-artifact@v4.1.9...v4.2.0
v4.1.9
Compare Source
What's Changed
New Contributors
Full Changelog: actions/download-artifact@v4.1.8...v4.1.9
v4.1.8
Compare Source
What's Changed
Full Changelog: actions/download-artifact@v4.1.7...v4.1.8
v4.1.7
Compare Source
What's Changed
Full Changelog: actions/download-artifact@v4.1.6...v4.1.7
v4.1.6
Compare Source
What's Changed
Full Changelog: actions/download-artifact@v4.1.5...v4.1.6
v4.1.5
Compare Source
What's Changed
Full Changelog: actions/download-artifact@v4.1.4...v4.1.5
v4.1.4
Compare Source
What's Changed
Full Changelog: actions/download-artifact@v4...v4.1.4
v4.1.3
Compare Source
What's Changed
New Contributors
Full Changelog: actions/download-artifact@v4...v4.1.3
v4.1.2
Compare Source
v4.1.1
Compare Source
v4.1.0
Compare Source
What's Changed
New Contributors
Full Changelog: actions/download-artifact@v4...v4.1.0
v4.0.0
Compare Source
What's Changed
The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.
ℹ️ However, this is a major update that includes breaking changes. Artifacts created with versions v3 and below are not compatible with the v4 actions. Uploads and downloads must use the same major actions versions. There are also key differences from previous versions that may require updates to your workflows.
For more information, please see:
Breaking Changes
For assistance with breaking changes, see MIGRATION.md.
Improvements
New Contributors
Full Changelog: actions/download-artifact@v3...v4.0.0
v4
Compare Source
v3.1.0
Compare Source
v3.1.0 - What's new
Node.js 24
This release updates the runtime to Node.js 24. The previous v3.0.2 ran on Node.js 16, which has reached end-of-life. Now this action will run on Node.js 24.
Pin your workflows to: https://github.com/actions/download-artifact/releases/tag/v3.1.0-node20 which is available if you're still in the process of phasing out Node 20.
What's Changed
Full Changelog: actions/download-artifact@v3.0.2...v3.1.0-node20
v3.0.2
Compare Source
v3.0.1
Compare Source
- Bump @actions/core to 1.10.0
actions/upload-artifact (actions/upload-artifact)v7.0.1
Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v7...v7.0.1
v7.0.0
Compare Source
v7 What's new
Direct Uploads
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.
What's Changed
New Contributors
Full Changelog: actions/upload-artifact@v6...v7.0.0
v7
Compare Source
v6.0.0
Compare Source
v6 - What's new
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
v6
Compare Source
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
v5
Compare Source
v4.6.2
Compare Source
What's Changed
New Contributors
Full Changelog: actions/upload-artifact@v4...v4.6.2
v4.6.1
Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4...v4.6.1
v4.6.0
Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4...v4.6.0
v4.5.0
Compare Source
What's Changed
New Contributors
Full Changelog: actions/upload-artifact@v4.4.3...v4.5.0
v4.4.3
Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4.4.2...v4.4.3
v4.4.2
Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4.4.1...v4.4.2
v4.4.1
Compare Source
What's Changed
New Contributors
Full Changelog: actions/upload-artifact@v4.4.0...v4.4.1
v4.4.0
Compare Source
Notice: Breaking Changes ⚠️
We will no longer include hidden files and folders by default in the upload-artifact action of this version. This reduces the risk that credentials are accidentally uploaded into artifacts. Customers who need to continue to upload these files can use a new option, include-hidden-files, to continue to do so.
See "Notice of upcoming deprecations and breaking changes in GitHub Actions runners" changelog and this issue for more details.
What's Changed
Full Changelog: actions/upload-artifact@v4.3.6...v4.4.0
v4.3.6
Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4...v4.3.6
v4.3.5
Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4.3.4...v4.3.5
v4.3.4
Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4.3.3...v4.3.4
v4.3.3
Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4.3.2...v4.3.3
v4.3.2
Compare Source
What's Changed
New Contributors
Full Changelog: actions/upload-artifact@v4.3.1...v4.3.2
v4.3.1
Compare Source
v4.3.0
Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4...v4.3.0
v4.2.0
Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4...v4.2.0
v4.1.0
Compare Source
What's Changed
New Contributors
Full Changelog: actions/upload-artifact@v4...v4.1.0
v4.0.0
Compare Source
What's Changed
The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.
ℹ️ However, this is a major update that includes breaking changes. Artifacts created with versions v3 and below are not compatible with the v4 actions. Uploads and downloads must use the same major actions versions. There are also key differences from previous versions that may require updates to your workflows.
For more information, please see:
New Contributors
Full Changelog: actions/upload-artifact@v3...v4.0.0
v4
Compare Source
v3.2.2
Compare Source
v3.2.2 - What's new
Node.js 24
This release updates the runtime to Node.js 24. The previous v3.2.1 ran on Node.js 16, which has reached end-of-life. Now this action will run on Node.js 24.
Pin your workflows to: https://github.com/actions/upload-artifact/releases/tag/v3.2.2-node20 which is available if you're still in the process of phasing out Node 20.
What's Changed
Full Changelog: actions/upload-artifact@v3.2.1...v3.2.2
v3.2.1
Compare Source
What's Changed
This fixes the include-hidden-files input introduced in https://github.com/actions/upload-artifact/releases/tag/v3.2.0
Full Changelog: actions/upload-artifact@v3.2.0...v3.2.1
v3.2.0
Compare Source
Notice: Breaking Changes ⚠️
We will no longer include hidden files and folders by default in the upload-artifact action of this version. This reduces the risk that credentials are accidentally uploaded into artifacts. Customers who need to continue to upload these files can use a new option, include-hidden-files, to continue to do so.
See "Notice of upcoming deprecations and breaking changes in GitHub Actions runners" changelog and this issue for more details.
What's Changed
Full Changelog: actions/upload-artifact@v3.1.3...v3.2.0
v3.1.3
Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v3...v3.1.3
v3.1.2
Compare Source
v3.1.1
Compare Source
v3.1.0
Compare Source
What's Changed
Configuration
📅 Schedule: (in timezone America/Los_Angeles)
🚦 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.