ci(deps): bump actions/download-artifact from 5 to 8

[dependabot]

Bumps actions/download-artifact from 5 to 8.

Release notes

Sourced from actions/download-artifact's releases.

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 actions/download-artifact#460
• Add a setting to specify what to do on hash mismatch and default it to error by @​danwkennedy in actions/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 actions/download-artifact#440
• Download Artifact Node24 support by @​salmanmkc in actions/download-artifact#415
• fix: update @​actions/artifact to fix Node.js 24 punycode deprecation by @​salmanmkc in actions/download-artifact#451
• prepare release v7.0.0 for Node.js 24 support by @​salmanmkc in actions/download-artifact#452

New Contributors

• @​patrikpolyak made their first contribution in actions/download-artifact#440
• @​salmanmkc made their first contribution in actions/download-artifact#415

Full Changelog: actions/download-artifact@v6.0.0...v7.0.0

v6.0.0

... (truncated)

Commits

• 3e5f45b Add regression tests for CJK characters (#471)
• e6d03f6 Add a regression test for artifact name + content-type mismatches (#472)
• 70fc10c Merge pull request #461 from actions/danwkennedy/digest-mismatch-behavior
• f258da9 Add change docs
• ccc058e Fix linting issues
• bd7976b Add a setting to specify what to do on hash mismatch and default it to error
• ac21fcf Merge pull request #460 from actions/danwkennedy/download-no-unzip
• 15999bf Add note about package bumps
• 974686e Bump the version to v8 and add release notes
• fbe48b1 Update test names to make it clearer what they do
• Additional commits viewable in compare view

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

[dependabot]

Labels

The following labels could not be found: dependencies, github-actions. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[its-spark-dev]

Holding this one for now — not because anything is wrong with it, but because this repository cannot currently prove it is right.

The other three Actions bumps have been merged (#2 checkout 5→7, #4 setup-python 6→7, #5 upload-artifact 4→7), and main is green on all six jobs. This one is different for a structural reason.

The green checks here do not exercise the change

actions/download-artifact is referenced exactly once in this repository, in release.yml, inside the attach job:

attach:
  needs: build
  if: startsWith(github.ref, 'refs/tags/v')   # <- only on a tag
  steps:
    - uses: actions/download-artifact@v5

release.yml triggers only on push: tags: ["v*"] and workflow_dispatch, and the attach job is additionally gated on the ref being a tag — so a workflow_dispatch run skips it too. Nothing that runs on pull_request or push: main touches this action.

Confirmed on this PR's own CI run: zero download-artifact steps were executed. The six passing checks are genuine, but they are green for reasons unrelated to the line this PR changes, so they carry no signal about it.

Why that matters for v8 specifically

v8.0.0 changes decompression behaviour:

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.

(v8.0.0 also makes digest mismatches an error by default, via the new digest-mismatch input. That one looks like a straightforward improvement.)

The decompression change lands directly on the step that turns the artifact back into individual files for the release upload:

- uses: actions/download-artifact@v5
  with: { name: release-distributions, path: dist }
...
  gh release upload "$GITHUB_REF_NAME" dist/* --clobber

If dist/ ends up holding one .zip instead of the wheel, the sdist and SHA256SUMS.txt, that command would attach the wrong thing to a release. The v4→v5 pair currently on main is the combination that produced the published v0.1.0 assets, so it is known-good; v8 against it is not yet demonstrated either way.

For the record, upload-artifact@v7 (#5) was merged because it is exercised by CI, and because its unzipped-upload feature is opt-in via a new archive input that this repository does not set — the artifact it produces was downloaded and verified to still be an ordinary ZIP containing both distributions.

What would clear this

Exercising the tag-gated path once, either by:

1. cutting a throwaway pre-release tag on a scratch branch and confirming the attach job still lands three separate files in dist/; or
2. temporarily relaxing the attach job's ref guard so workflow_dispatch can run it end to end.

Planned to be re-reviewed alongside that release-pipeline validation, before the next tagged release. Leaving this open in the meantime — please keep rebasing or recreating it as usual, and no action is needed from Dependabot.