chore(deps): Bump actions/download-artifact from 4 to 8

[dependabot]

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

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[oratis]

Deferring (low-risk, but same rationale as #156): actions/cache@v4→v5 is only in release.yml, which I can't exercise without a real release run. Cache is non-fatal so the risk is small — fine to merge alongside the other release-workflow bumps when the maintainer next cuts a release + can watch it.

[oratis]

@dependabot rebase

[oratis]

Review: approved ✅ — and this one is worth more than a routine bump

actions/download-artifact v4 → v8. This closes a version skew that #208 introduced: release.yml now uploads with actions/upload-artifact@v7 (lines 137 and 242, the VSIX and the DMG) while the github-release job downloaded with v4.

I checked whether that skew was actually broken, and it is not — upload-artifact@v7's direct/unzipped upload is opt-in via archive: false, which this repo does not set, so v7 still produces zipped artifacts that a v4 download can unzip. So this is hygiene, not a release-blocker. I'd rather state that precisely than merge it on a wrong premise.

What genuinely improves:

• v8 defaults digest-mismatch to error. Previously a hash mismatch on a downloaded artifact only logged a warning. For the github-release job — which downloads the DMG and VSIX and publishes them — silently attaching a corrupted artifact was the bad outcome. Failing the run is the right default for a publish step.
• Upload and download generations are now adjacent (v7/v8) instead of three majors apart.

Heads-up for the first release on this: the stricter digest check is a new failure mode. If a release run fails at the download step with a hash mismatch, that is this change surfacing real artifact corruption rather than a regression in the bump — re-run rather than reaching for digest-mismatch: warn.

Note: the pre-rebase branch bumped only 1 of the 2 download-artifact uses (it predated the second one). I had Dependabot rebase; the merged diff now covers both.

Rebased, CI green.