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

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 false.

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

• 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
• 96bf374 One more test fix
• b8c4819 Fix skip decompress test
• 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)

[github-actions]

🤖 Cursor Dependency Analysis

The grep results show no hits in the actual repo workflows. Let me verify by checking the workflow files directly and the upstream action definition.Let me read the full workflow file to understand the usage context.Here is my analysis:

---

Dependabot PR Review: actions/download-artifact v7 -> v8

1. Usage Sites

Single usage in the repo:

        uses: actions/download-artifact@v8
        with:
          name: build
          path: ./build

The usage is minimal -- it downloads a single named artifact (build) to a specific path. Only name and path inputs are used; no advanced options.

2. API Intersection with Breaking Changes

v8 breaking changes vs. this repo's usage:

• Direct downloads (no auto-unzip of non-zipped files): The artifact is uploaded via actions/upload-artifact@v6 (line 46), which produces standard zipped artifacts. v8's download action checks Content-Type before unzipping, so standard zipped artifacts will continue to be unzipped as before. No impact.
• Enforced digest checks (default changed from warn to error): This is the most relevant change. If a downloaded artifact's hash doesn't match the server-reported hash, the workflow will now fail instead of logging a warning. This is more secure but could surface latent issues. The name and path inputs are unchanged. Low risk -- hash mismatches should not occur under normal conditions and would indicate a real integrity problem.
• ESM migration: Internal packaging change. No impact on callers.

The action.yml in .upstream-dependency confirms all existing inputs (name, path) remain with the same semantics. Two new optional inputs were added (skip-decompress, digest-mismatch) with sensible defaults.

3. Risks / Unknowns

• Upload/download version pairing: The upload step uses actions/upload-artifact@v6 while download moves to v8. These are different actions with independent versioning and are designed to interoperate via the GitHub Artifacts API, so this mismatch in major version numbers is cosmetic, not functional.
• Digest enforcement: If there were previously silent hash mismatches (logged as warnings in v7), they will now cause failures. This is a security improvement but could surface unexpected failures. If this occurs, the new digest-mismatch input can be set to warn as a workaround.
• node24 runtime: v8 runs on node24 (per action.yml). GitHub-hosted runners support this, but if any self-hosted runners in the pipeline are on older Node runtimes, there could be an issue. The deploy-review.yml uses ubuntu-latest for the package job where download-artifact is called, so this is fine.

4. Recommendation

Merge. The usage is simple (only name + path), none of the breaking changes affect the inputs/outputs used here, and the digest enforcement is a security improvement with sensible defaults. No code changes are needed beyond the version bump.