chore(ci): bump actions/download-artifact from 4.3.0 to 8.0.1#82
chore(ci): bump actions/download-artifact from 4.3.0 to 8.0.1#82dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 4.3.0 to 8.0.1. - [Release notes](https://github.com/actions/download-artifact/releases) - [Commits](actions/download-artifact@d3f86a1...3e5f45b) --- updated-dependencies: - dependency-name: actions/download-artifact dependency-version: 8.0.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
lml2468
left a comment
There was a problem hiding this comment.
[COMMENT] Version verified ✅ — is a legitimate release in the official repo.
Note: Same as noted on PR #81 — recommend merging #81 (upload-artifact v7) and #82 (download-artifact v8) together. If you choose to merge only one, the cross-major compatibility guarantee should hold, but pairing them is cleaner.
Jerry-Xin
left a comment
There was a problem hiding this comment.
Summary: Project relevance gate passed; this PR updates an in-scope Docker publishing workflow dependency and is safe for the current workflow shape.
💬 Non-blocking
- 🔵 Suggestion:
.github/workflows/docker-publish.yml:207actions/download-artifact@v8runs on Node.js 24, so this remains fine while the job uses GitHub-hostedubuntu-latest; if this workflow is ever moved to self-hosted runners, runner version compatibility should be checked first. - 🔵 Suggestion:
.github/workflows/docker-publish.yml:207The v8 artifact extraction behavior is compatible here: the artifacts are uploaded in the same workflow byactions/upload-artifact@v4.6.2, and GitHub’s non-zipped artifact behavior applies to newer upload-artifact usage with unarchived uploads, while older/default artifacts continue to be zipped. (github.blog)
✅ Highlights
- The action is pinned to the exact v8.0.1 commit SHA, matching the repository’s existing supply-chain hardening style.
- Existing
pattern: digests-*andmerge-multiple: trueusage still matches the intended two digest artifacts before manifest creation. - No additional tests are needed for this dependency-only workflow update; the main validation is a successful Docker publish workflow run.
lml2468
left a comment
There was a problem hiding this comment.
Cross-review (qijingchun) — No issues. SHA-pinned bump (actions/download-artifact v4.3.0 → v8.0.1). COMMENTED.
Bumps actions/download-artifact from 4.3.0 to 8.0.1.
Release notes
Sourced from actions/download-artifact's releases.
... (truncated)
Commits
3e5f45bAdd regression tests for CJK characters (#471)e6d03f6Add a regression test for artifact name + content-type mismatches (#472)70fc10cMerge pull request #461 from actions/danwkennedy/digest-mismatch-behaviorf258da9Add change docsccc058eFix linting issuesbd7976bAdd a setting to specify what to do on hash mismatch and default it toerrorac21fcfMerge pull request #460 from actions/danwkennedy/download-no-unzip15999bfAdd note about package bumps974686eBump the version tov8and add release notesfbe48b1Update test names to make it clearer what they doDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)