Skip to content

chore(deps): update actions/download-artifact action to v5#6068

Merged
lukastaegert merged 1 commit intomasterfrom
renovate/major-github-artifact-actions
Aug 17, 2025
Merged

chore(deps): update actions/download-artifact action to v5#6068
lukastaegert merged 1 commit intomasterfrom
renovate/major-github-artifact-actions

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Aug 15, 2025

This PR contains the following updates:

Package Type Update Change
actions/download-artifact action major v4.3.0 -> v5.0.0

Release Notes

actions/download-artifact (actions/download-artifact)

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


Configuration

📅 Schedule: Branch creation - "before 4am on Friday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@vercel
Copy link
Copy Markdown

vercel Bot commented Aug 15, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
rollup Ready Ready Preview Comment Aug 17, 2025 5:47am

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Aug 15, 2025

Thank you for your contribution! ❤️

You can try out this pull request locally by installing Rollup via

npm install rollup/rollup#renovate/major-github-artifact-actions

Notice: Ensure you have installed the latest nightly Rust toolchain. If you haven't installed it yet, please see https://www.rust-lang.org/tools/install to learn how to download Rustup and install Rust.

or load it into the REPL:
https://rollup-2tyrewwok-rollup-js.vercel.app/repl/?pr=6068

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Aug 15, 2025

Performance report

  • BUILD: 6912ms (-177ms, -2.5%), 834 MB (+4%)
    • initialize: 0ms, 24.8 MB
    • generate module graph: 2584ms, 630 MB
      • generate ast: 1371ms, 622 MB
    • sort and bind modules: 386ms, 687 MB
    • mark included statements: 3942ms (-167ms, -4.1%), 834 MB (+4%)
      • treeshaking pass 1: 2312ms (-135ms, -5.5%), 822 MB
      • treeshaking pass 2: 460ms, 835 MB (+3%)
      • treeshaking pass 3: 396ms, 826 MB (+3%)
      • treeshaking pass 4: 382ms, 831 MB (+3%)
      • treeshaking pass 5: 378ms, 834 MB (+4%)
  • GENERATE: 912ms (+222ms, +32.2%), 937 MB (-2%)
    • initialize render: 0ms, 948 MB (+4%)
    • generate chunks: 76ms (+28ms, +58.6%), 944 MB (+4%)
      • optimize chunks: 0ms, 931 MB (+4%)
    • render chunks: 779ms (+165ms, +26.8%), 915 MB
    • transform chunks: 19ms, 937 MB (-2%)
    • generate bundle: 0ms, 937 MB (-2%)

@codecov
Copy link
Copy Markdown

codecov Bot commented Aug 15, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.79%. Comparing base (e4082a8) to head (dfc0e15).
⚠️ Report is 1 commits behind head on master.

⚠️ Current head dfc0e15 differs from pull request most recent head 9bce0f7

Please upload reports for the commit 9bce0f7 to get more accurate results.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #6068   +/-   ##
=======================================
  Coverage   98.79%   98.79%           
=======================================
  Files         271      271           
  Lines       10601    10601           
  Branches     2830     2830           
=======================================
  Hits        10473    10473           
  Misses         88       88           
  Partials       40       40           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate renovate Bot force-pushed the renovate/major-github-artifact-actions branch from dfc0e15 to 9bce0f7 Compare August 17, 2025 05:42
@lukastaegert lukastaegert enabled auto-merge August 17, 2025 05:42
@lukastaegert lukastaegert disabled auto-merge August 17, 2025 07:57
@lukastaegert lukastaegert merged commit 682d799 into master Aug 17, 2025
75 checks passed
@lukastaegert lukastaegert deleted the renovate/major-github-artifact-actions branch August 17, 2025 07:57
@github-actions
Copy link
Copy Markdown

This PR has been released as part of rollup@4.46.3. You can test it via npm install rollup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant