ci(deps): bump actions/download-artifact from 4.1.7 to 8.0.1#205
Conversation
Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 4.1.7 to 8.0.1. - [Release notes](https://github.com/actions/download-artifact/releases) - [Commits](actions/download-artifact@65a9edc...3e5f45b) --- updated-dependencies: - dependency-name: actions/download-artifact dependency-version: 8.0.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
| Field | Value |
|---|---|
| Action | actions/download-artifact |
| Previous | v4.1.7 |
| New | v8.0.1 |
| Type | Major (v4 → v8) |
Breaking Changes
-
Enforced checks (breaking)
- BREAKING CHANGE: this update supports Node
v24.x. This is not a breaking change per-se but we're treating it as such. -
- BREAKING fix: inconsistent path behavior for single artifact downloads by ID by @GrantBirki in fix: inconsistent path behavior for single artifact downloads by ID actions/download-artifact#416
-
🚨 Breaking Change
-
Migration Guide
Release Notes (v5 → v8)
v8.0.1
What's Changed
- Support for CJK characters in the artifact name by @danwkennedy in Add regression tests for CJK characters actions/download-artifact#471
- Add a regression test for artifact name + content-type mismatches by @danwkennedy in Add a regression test for artifact name + content-type mismatches actions/download-artifact#472
Full Changelog: actions/download-artifact@v8...v8.0.1
v8.0.0
v8 - What's new
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.
What's Changed
- Don't attempt to un-zip non-zipped downloads by @danwkennedy in Don't attempt to un-zip non-zipped downloads actions/download-artifact#460
- Add a setting to specify what to do on hash mismatch and default it to
errorby @danwkennedy in Add a setting to specify what to do on hash mismatch and default it toerroractions/download-artifact#461
Full Changelog: actions/download-artifact@v7...v8.0.0
v7.0.0
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
- Update GHES guidance to include reference to Node 20 version by @patrikpolyak in Update GHES guidance to include reference to Node 20 version actions/download-artifact#440
- Download Artifact Node24 support by @salmanmkc in Download Artifact Node24 support actions/download-artifact#415
- fix: update @actions/artifact to fix Node.js 24 punycode deprecation by @salmanmkc in fix: update @actions/artifact to fix Node.js 24 punycode deprecation actions/download-artifact#451
- prepare release v7.0.0 for Node.js 24 support by @salmanmkc in prepare release v7.0.0 for Node.js 24 support actions/download-artifact#452
New Contributors
- @patrikpolyak made their first contribution in Update GHES guidance to include reference to Node 20 version actions/download-artifact#440
- @salmanmkc made their first contribution in Download Artifact Node24 support actions/download-artifact#415
Full Changelog: actions/download-artifact@v6.0.0...v7.0.0
v6.0.0
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.
- Update README for download-artifact v5 changes by @yacaovsnc in Update README for download-artifact v5 changes actions/download-artifact#417
- Update README with artifact extraction details by @yacaovsnc in Update README with artifact extraction details actions/download-artifact#424
- Readme: spell out the first use of GHES by @danwkennedy in Readme: spell out the first use of GHES actions/download-artifact#431
- Bump
@actions/artifacttov4.0.0 - Prepare
v6.0.0by @danwkennedy in Preparev6.0.0actions/download-artifact#438
New Contributors
- @danwkennedy made their first contribution in Readme: spell out the first use of GHES actions/download-artifact#431
Full Changelog: actions/download-artifact@v5...v6.0.0
v5.0.0
What's Changed
- Update README.md by @nebuk89 in Update README.md actions/download-artifact#407
- BREAKING fix: inconsistent path behavior for single artifact downloads by ID by @GrantBirki in fix: inconsistent path behavior for single artifact downloads by ID actions/download-artifact#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 topath/(direct) - By ID:
artifact-ids: 12345→ extracted topath/my-artifact/(nested)
Now both methods are consistent:
- By name:
name: my-artifact→ extracted topath/(unchanged) - By ID:
artifact-ids: 12345→ extracted topath/(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: trueas 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-artifactis 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 pathNew Contributors
- @nebuk89 made their first contribution in Update README.md actions/download-artifact#407
Full Changelog: actions/download-artifact@v4...v5.0.0
Next Steps
- Review breaking changes above
- Check if workflow inputs/outputs changed
- Verify compatibility with your CI/CD configuration
Full changelog: https://github.com/actions/download-artifact/releases
Generated automatically for Dependabot major version PRs.
commit: |
jpr5
deleted the
dependabot/github_actions/actions/download-artifact-8.0.1
branch
1 participant
Bumps actions/download-artifact from 4.1.7 to 8.0.1.
Release notes
Sourced from actions/download-artifact's releases.
... (truncated)
Commits
3e5f45bAdd regression tests for CJK characters (#471)e6d03f6Add a regression test for artifact name + content-type mismatches (#472)70fc10cMerge pull request #461 from actions/danwkennedy/digest-mismatch-behaviorf258da9Add change docsccc058eFix linting issuesbd7976bAdd a setting to specify what to do on hash mismatch and default it toerrorac21fcfMerge pull request #460 from actions/danwkennedy/download-no-unzip15999bfAdd note about package bumps974686eBump the version tov8and add release notesfbe48b1Update test names to make it clearer what they doDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)