Skip to content

chore(deps): bump actions/download-artifact from 4 to 8#117

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/download-artifact-8
Closed

chore(deps): bump actions/download-artifact from 4 to 8#117
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/download-artifact-8

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 10, 2026

Copy link
Copy Markdown
Contributor

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

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

New Contributors

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 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 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 8.
- [Release notes](https://github.com/actions/download-artifact/releases)
- [Commits](actions/download-artifact@v4...v8)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jun 10, 2026
@wiiiimm

wiiiimm commented Jun 18, 2026

Copy link
Copy Markdown
Owner

Superseded by #131, which consolidates all open Dependabot updates into a single PR. Closing in favour of that.

@wiiiimm wiiiimm closed this Jun 18, 2026
@dependabot @github

dependabot Bot commented on behalf of github Jun 18, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot Bot deleted the dependabot/github_actions/actions/download-artifact-8 branch June 18, 2026 06:05
wiiiimm added a commit that referenced this pull request Jun 18, 2026
…r title] (#131)

* chore(deps): consolidate open dependabot updates (GMC-45)

Combine all 13 open Dependabot PRs (#116#129) into a single update.

npm group (#129): @octokit/graphql 9.0.3, apollo3-cache-persist 0.15.0,
chalk 5.6.2, dotenv 17.4.2, fuse.js 7.4.2, react 19.2.7,
@types/react 19.2.17, tsup 8.5.1, vitest 4.1.9.

npm majors: typescript 6.0.3 (#128), @vitest/coverage-v8 4.1.8 (#127),
semantic-release 25.0.5 (#126), ink-testing-library 4.0.0 (#125),
env-paths 4.0.0 (#124), @types/node 25.9.2 (#123), open 11.0.0 (#122).

GitHub Actions: setup-node v6 (#120), checkout v6 (#119),
github-script v9 (#118), download-artifact v8 (#117), cache v5 (#116).

Verified: typecheck (TS 6), build, and full test suite (456/456) all pass.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* ci: bump release workflow to Node 22 for semantic-release 25 (GMC-45)

semantic-release 25 requires Node ^22.14.0 || >=24.10.0; the release
workflow still set up Node 20, which would fail `npx semantic-release`
on the next push to main. Bump all setup-node steps to Node 22 (LTS).

Flagged by Cursor Bugbot (High) and Codex (P1) on PR #131.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* chore: raise Node floor to >=20 for env-paths 4 and open 11 (GMC-45)

env-paths@4 and open@11 both declare engines.node ">=20", but the
package still advertised ">=18", letting Node 18-19 users install a
build that breaks at startup (env-paths) and on browser open (open).
Align engines.node and the setup docs to >=20. Node 18 is already EOL.

Flagged by Cursor Bugbot (Medium) on PR #131.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* build: migrate to @yao-pkg/pkg and target node20 binaries (GMC-45)

vercel/pkg (pkg@5.8.1) is archived and only ships base binaries up to
Node 18, so release binaries embedded a Node 18 runtime — incompatible
with env-paths 4 / open 11 (Node 20+) after raising the engine floor.
Switch to the maintained @yao-pkg/pkg fork and build node20 targets in
both the build:binaries script and the release workflow. The packager
needs Node 22 to run, which the release jobs already use.

Flagged by Cursor Bugbot (High) on PR #131.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs: note build:binaries requires Node 22+ for @yao-pkg/pkg (GMC-45)

The CLI runtime engine stays at Node >=20, but @yao-pkg/pkg requires
Node >=22 to run. Document this in the Packaging section so contributors
on Node 20/21 know the binary build needs a newer Node, rather than
raising engines.node and wrongly forcing end users onto Node 22.

Addresses CodeRabbit engine-mismatch note on PR #131. The companion
"Invalid Windows pkg target" finding is a false positive: pkg-fetch's
toFancyPlatform aliases "windows" -> "win" during target parsing.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

1 participant