Sourced from actions/download-artifact's releases.
v5.0.0
What's Changed
- Update README.md by
@nebuk89
in actions/download-artifact#407- BREAKING fix: inconsistent path behavior for single artifact downloads by ID by
@GrantBirki
in actions/download-artifact#416v5.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: 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 uploadedTo maintain old behavior (if needed):
</tr></table>
... (truncated)
634f93c
Merge pull request #416
from actions/single-artifact-id-download-pathb19ff43
refactor: resolve download path correctly in artifact download tests
(mainly ...e262cbe
bundle distbff23f9
update docsfff8c14
fix download path logic when downloading a single artifact by id448e3f8
Merge pull request #407
from actions/nebuk89-patch-147225c4
Update README.md