Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 1, 2025

Bumps actions/download-artifact from 4 to 5.

Release notes

Sourced from actions/download-artifact's releases.

v5.0.0

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):

</tr></table> 

... (truncated)

Commits
  • 634f93c Merge pull request #416 from actions/single-artifact-id-download-path
  • b19ff43 refactor: resolve download path correctly in artifact download tests (mainly ...
  • e262cbe bundle dist
  • bff23f9 update docs
  • fff8c14 fix download path logic when downloading a single artifact by id
  • 448e3f8 Merge pull request #407 from actions/nebuk89-patch-1
  • 47225c4 Update README.md
  • See full diff in compare view

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 4 to 5.
- [Release notes](https://github.com/actions/download-artifact/releases)
- [Commits](actions/download-artifact@v4...v5)

---
updated-dependencies:
- dependency-name: actions/download-artifact
  dependency-version: '5'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Sep 1, 2025
@pnuu
Copy link
Member

pnuu commented Sep 1, 2025

Failure in windows tests:

Windows fatal exception: code 0xc06d007e

Current thread 0x00000eec (most recent call first):
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\scipy\linalg\_basic.py", line 1495 in lstsq
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\scipy\_lib\_util.py", line 1233 in wrapper
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\scipy\sparse\linalg\_isolve\_gcrotmk.py", line 177 in _fgmres
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\scipy\sparse\linalg\_isolve\_gcrotmk.py", line 395 in gcrotmk
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\scipy\interpolate\_ndbspline.py", line 339 in _iter_solve
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\scipy\interpolate\_ndbspline.py", line 412 in make_ndbspl
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\scipy\interpolate\_rgi.py", line 309 in _construct_spline
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\scipy\interpolate\_rgi.py", line 405 in __call__
  File "D:\a\python-geotiepoints\python-geotiepoints\geotiepoints\interpolator.py", line 339 in interpolate_numpy
  File "D:\a\python-geotiepoints\python-geotiepoints\geotiepoints\interpolator.py", line 271 in interpolate
  File "D:\a\python-geotiepoints\python-geotiepoints\geotiepoints\interpolator.py", line 370 in <genexpr>
  File "D:\a\python-geotiepoints\python-geotiepoints\geotiepoints\geointerpolator.py", line 107 in interpolate
  File "D:\a\python-geotiepoints\python-geotiepoints\geotiepoints\interpolator.py", line 375 in interpolate_to_shape
  File "D:\a\python-geotiepoints\python-geotiepoints\geotiepoints\tests\test_geointerpolator.py", line 291 in test_geogrid_interpolation_can_extrapolate
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\_pytest\python.py", line 157 in pytest_pyfunc_call
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_callers.py", line 121 in _multicall
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_manager.py", line 120 in _hookexec
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_hooks.py", line 512 in __call__
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\_pytest\python.py", line 1671 in runtest
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\_pytest\runner.py", line 178 in pytest_runtest_call
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_callers.py", line 121 in _multicall
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_manager.py", line 120 in _hookexec
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_hooks.py", line 512 in __call__
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\_pytest\runner.py", line 246 in <lambda>
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\_pytest\runner.py", line 344 in from_call
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\_pytest\runner.py", line 245 in call_and_report
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\_pytest\runner.py", line 136 in runtestprotocol
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\_pytest\runner.py", line 117 in pytest_runtest_protocol
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_callers.py", line 121 in _multicall
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_manager.py", line 120 in _hookexec
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_hooks.py", line 512 in __call__
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\_pytest\main.py", line 367 in pytest_runtestloop
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_callers.py", line 121 in _multicall
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_manager.py", line 120 in _hookexec
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_hooks.py", line 512 in __call__
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\_pytest\main.py", line 343 in _main
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\_pytest\main.py", line 289 in wrap_session
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\_pytest\main.py", line 336 in pytest_cmdline_main
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_callers.py", line 121 in _multicall
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_manager.py", line 120 in _hookexec
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\pluggy\_hooks.py", line 512 in __call__
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\_pytest\config\__init__.py", line 175 in main
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Lib\site-packages\_pytest\config\__init__.py", line 201 in console_main
  File "C:\Users\runneradmin\miniconda3\envs\test-environment\Scripts\pytest-script.py", line 10 in <module>
geotiepoints\tests\test_geointerpolator.py ...........
Error: Process completed with exit code 127.

@coveralls
Copy link

Coverage Status

coverage: 87.965%. remained the same
when pulling 95076ad on dependabot/github_actions/actions/download-artifact-5
into b29c01a on main.

@djhoese djhoese merged commit 2273804 into main Sep 2, 2025
39 checks passed
@djhoese djhoese deleted the dependabot/github_actions/actions/download-artifact-5 branch September 2, 2025 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants