chore(deps): bump actions/download-artifact from 7 to 8

[dependabot]

Bumps actions/download-artifact from 7 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

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

[claude]

Claude finished @dependabot[bot]'s task in 1m 5s —— View job

---

Review: actions/download-artifact v7 → v8

• Identify the exact change in this PR
• Review v8 breaking changes against codebase usage
• Search for all download-artifact usages in the repo
• Assess risk and provide recommendation

---

Change Summary

Single-line change in .github/workflows/docker.yml:205 — bumps actions/download-artifact from v7 to v8. This step downloads per-architecture Docker digest artifacts (empty files named by SHA) with pattern: digest-* and merge-multiple: true.

v8 Breaking Changes vs. This Repo

v8 Change	Risk to this repo	Notes
Hash mismatch defaults to error (was warn)	Low — net positive	More strict integrity checking. If a digest hash doesn't match, the workflow fails fast instead of silently continuing. This is the desired behavior for a security-conscious CI pipeline.
Non-zipped files skip decompression	None	Files uploaded by upload-artifact v4+ are always transmitted as zips. The v8 download action checks Content-Type and decompresses zips as before. Only "direct uploads" (a new v8 upload feature) skip zipping. Since upload is still at v7, all artifacts are zipped normally.
ESM module migration	None	Transparent to callers — only affects forks of the action itself.

Cross-Version Compatibility

The upload step in docker.yml:165 still uses actions/upload-artifact@v7. This is fine — both v4+ upload and v4+ download use the same Artifacts v4 backend API. The v8 download changes are about client-side handling (decompression, hash checking), not the wire protocol. Additionally, binary_provenance.yml:44 already uses download-artifact@v8 in this repo, so there's existing precedent.

Parameters Check

The parameters used in this step (path, pattern, merge-multiple) are all supported in v8 with no behavioral changes.

Recommendation

Safe to merge. The upgrade improves security (hash mismatch → error) with no functional risk to this repo's usage. No code changes or new parameters needed.

Optional follow-up: Consider bumping actions/upload-artifact from v7 to v8 as well (in docker.yml:165 and release.yml:164) to keep versions aligned, though it's not required for correctness.

[dangrondahl]

@dependabot rebase