You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
[!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 #440
BREAKING fix: inconsistent path behavior for single artifact downloads by ID by @GrantBirki in #416
v5.0.0
🚨 Breaking Change
This release fixes an inconsistency in path behavior for single artifact downloads by ID. If you're downloading single artifacts by ID, the output path may change.
What Changed
Previously, single artifact downloads behaved differently depending on how you specified the artifact:
By name: name: my-artifact → extracted to path/ (direct)
By ID: artifact-ids: 12345 → extracted to path/my-artifact/ (nested)
Now both methods are consistent:
By name: name: my-artifact → extracted to path/ (unchanged)
By ID: artifact-ids: 12345 → extracted to path/ (fixed - now direct)
Migration Guide
✅ No Action Needed If:
You download artifacts by name
You download multiple artifacts by ID
You already use merge-multiple: true as a workaround
⚠️ Action Required If:
You download single artifacts by ID and your workflows expect the nested directory structure.
Before v5 (nested structure):
- uses: actions/download-artifact@v4with:
artifact-ids: 12345path: dist### Files were in: dist/my-artifact/
Where my-artifact is the name of the artifact you previously uploaded
Adds support for uploading single files directly (unzipped). Callers can set the new archive parameter to false to skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. The name parameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.
ESM
To support new versions of the @actions/* packages, we've upgraded the package to ESM.
We will no longer include hidden files and folders by default in the upload-artifact action of this version. This reduces the risk that credentials are accidentally uploaded into artifacts. Customers who need to continue to upload these files can use a new option, include-hidden-files, to continue to do so.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Security Review: No issues found
This PR updates first-party GitHub artifact actions (actions/upload-artifact v4→v7, actions/download-artifact v4→v8) in the CI workflow. These are maintained by the GitHub actions/ organization.
No new permissions, secrets, or workflow triggers are introduced.
No new code paths or logic changes — only version strings in uses: directives.
The existing pattern of using mutable major-version tags (rather than SHA-pinned refs) is unchanged; this is a pre-existing posture, not a new risk from this PR.
Scope: Single file changed (.github/workflows/dev.yml) — version bumps only, no logic changes.
Assessment:
Both actions/upload-artifact and actions/download-artifact are first-party GitHub Actions maintained by the actions/ organization. The referenced versions (v7.0.1 and v8.0.1 respectively) are legitimate, published releases.
The download-artifact@v8 update actually improves security posture: it now defaults digest-mismatch to error, enforcing artifact integrity checks that were previously only warnings.
The use of mutable major-version tags (@v7, @v8) follows the same pattern as the previous @v4 references — this is not a new risk introduced by the PR.
No injection risks, secret leakage, permission changes, or supply-chain concerns identified.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Security Review: No Issues Found
This PR bumps two first-party GitHub Actions (actions/upload-artifact v4 → v7, actions/download-artifact v4 → v8) in .github/workflows/dev.yml. Both are official, verified releases from the actions organization.
Supply-chain risk: Low. These are first-party GitHub Actions with verified signatures. The use of major version tags (e.g., v7, v8) rather than pinned SHAs is consistent with the existing pattern and is standard for official actions.
Security improvement: download-artifact@v8 now defaults digest-mismatch behavior to error, which strengthens artifact integrity checks.
No new permissions, secrets exposure, code execution paths, or injection vectors are introduced by this change.
The reason will be displayed to describe this comment to others. Learn more.
Security review (automation)
Scope:.github/workflows/dev.yml only bumps first-party GitHub actions: actions/upload-artifact@v4 → @v7 and actions/download-artifact@v4 → @v8. No workflow logic, permissions, triggers, or step inputs (name, path, etc.) were changed in this diff.
Findings: None rated medium or higher.
Analysis (concise):
Injection / SSRF / secrets: These edits only change action major versions; they do not introduce new attacker-controlled sinks or logging.
Authn/authz: Unchanged; deploy jobs remain gated with if: github.repository_owner == 'semaphoreui'.
Supply chain: Still actions/* maintained by GitHub; same trust model as the prior @v4 pins. download-artifact v8 tightens integrity handling (hash mismatch defaults to error per upstream release notes), which is security-positive rather than a regression.
Prior automation threads: Cleaned up so this assessment is the active one.
Slack (paste-ready): PR 3442 security review: clean — dependency-only bump to official upload-artifact / download-artifact majors; no new medium+ issues identified.
Sent by Cursor Automation: Find vulnerabilities
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
renovate
Bot
force-pushed
the
renovate/major-github-artifact-actions
branch
from
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This PR contains the following updates:
v4→v8v4→v7Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
actions/download-artifact (actions/download-artifact)
v8.0.1Compare Source
What's Changed
Full Changelog: actions/download-artifact@v8...v8.0.1
v8.0.0Compare Source
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 theContent-Typeheader ahead of unzipping and skips non-zipped files. Callers wishing to download a zipped file as-is can also set the newskip-decompressparameter tofalse.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-mismatchparameter. To be secure by default, we are now defaulting the behavior toerrorwhich will fail the workflow run.ESM
To support new versions of the @actions/* packages, we've upgraded the package to ESM.
What's Changed
errorby @danwkennedy in #461Full Changelog: actions/download-artifact@v7...v8.0.0
v8Compare Source
v7.0.0Compare Source
v7 - What's new
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
v7Compare Source
v6.0.0Compare Source
What's Changed
BREAKING CHANGE: this update supports Node
v24.x. This is not a breaking change per-se but we're treating it as such.@actions/artifacttov4.0.0v6.0.0by @danwkennedy in #438New Contributors
Full Changelog: actions/download-artifact@v5...v6.0.0
v6Compare Source
v5.0.0Compare Source
What's Changed
v5.0.0
🚨 Breaking Change
This release fixes an inconsistency in path behavior for single artifact downloads by ID. If you're downloading single artifacts by ID, the output path may change.
What Changed
Previously, single artifact downloads behaved differently depending on how you specified the artifact:
name: my-artifact→ extracted topath/(direct)artifact-ids: 12345→ extracted topath/my-artifact/(nested)Now both methods are consistent:
name: my-artifact→ extracted topath/(unchanged)artifact-ids: 12345→ extracted topath/(fixed - now direct)Migration Guide
✅ No Action Needed If:
merge-multiple: trueas a workaroundYou download single artifacts by ID and your workflows expect the nested directory structure.
Before v5 (nested structure):
To maintain old behavior (if needed):
New Contributors
Full Changelog: actions/download-artifact@v4...v5.0.0
v5Compare Source
v4.3.0Compare Source
What's Changed
artifact-idsinput by @GrantBirki in #401New Contributors
Full Changelog: actions/download-artifact@v4.2.1...v4.3.0
v4.2.1Compare Source
What's Changed
Full Changelog: actions/download-artifact@v4.2.0...v4.2.1
v4.2.0Compare Source
What's Changed
New Contributors
Full Changelog: actions/download-artifact@v4.1.9...v4.2.0
v4.1.9Compare Source
What's Changed
New Contributors
Full Changelog: actions/download-artifact@v4.1.8...v4.1.9
v4.1.8Compare Source
What's Changed
Full Changelog: actions/download-artifact@v4.1.7...v4.1.8
v4.1.7Compare Source
What's Changed
Full Changelog: actions/download-artifact@v4.1.6...v4.1.7
v4.1.6Compare Source
What's Changed
@actions/artifactdependency to v2.1.6 by @eggyhead in #324Full Changelog: actions/download-artifact@v4.1.5...v4.1.6
v4.1.5Compare Source
What's Changed
@actions/coreto v1.10.1 and@actions/artifactto v2.1.5Full Changelog: actions/download-artifact@v4.1.4...v4.1.5
v4.1.4Compare Source
What's Changed
Full Changelog: actions/download-artifact@v4...v4.1.4
v4.1.3Compare Source
What's Changed
New Contributors
Full Changelog: actions/download-artifact@v4...v4.1.3
v4.1.2Compare Source
v4.1.1Compare Source
@actions/artifactsto latest versionv4.1.0Compare Source
What's Changed
New Contributors
Full Changelog: actions/download-artifact@v4...v4.1.0
actions/upload-artifact (actions/upload-artifact)
v7.0.1Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v7...v7.0.1
v7.0.0Compare Source
v7 What's new
Direct Uploads
Adds support for uploading single files directly (unzipped). Callers can set the new
archiveparameter tofalseto skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. Thenameparameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.ESM
To support new versions of the
@actions/*packages, we've upgraded the package to ESM.What's Changed
New Contributors
Full Changelog: actions/upload-artifact@v6...v7.0.0
v7Compare Source
v6.0.0Compare Source
v6Compare Source
v5.0.0Compare Source
v5Compare Source
v4.6.2Compare Source
What's Changed
New Contributors
Full Changelog: actions/upload-artifact@v4...v4.6.2
v4.6.1Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4...v4.6.1
v4.6.0Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4...v4.6.0
v4.5.0Compare Source
What's Changed
Node.jsversion in action by @hamirmahal in #578artifact-digestoutput by @bdehamer in #656New Contributors
Full Changelog: actions/upload-artifact@v4.4.3...v4.5.0
v4.4.3Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4.4.2...v4.4.3
v4.4.2Compare Source
What's Changed
@actions/artifactto 2.1.11 by @robherley in #627Full Changelog: actions/upload-artifact@v4.4.1...v4.4.2
v4.4.1Compare Source
What's Changed
New Contributors
Full Changelog: actions/upload-artifact@v4.4.0...v4.4.1
v4.4.0Compare Source
Notice: Breaking Changes⚠️
We will no longer include hidden files and folders by default in the
upload-artifactaction of this version. This reduces the risk that credentials are accidentally uploaded into artifacts. Customers who need to continue to upload these files can use a new option,include-hidden-files, to continue to do so.See "Notice of upcoming deprecations and breaking changes in GitHub Actions runners" changelog and this issue for more details.
What's Changed
Full Changelog: actions/upload-artifact@v4.3.6...v4.4.0
v4.3.6Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4...v4.3.6
v4.3.5Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4.3.4...v4.3.5
v4.3.4Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4.3.3...v4.3.4
v4.3.3Compare Source
What's Changed
@actions/artifactdependency to v2.1.6 by @eggyhead in #565Full Changelog: actions/upload-artifact@v4.3.2...v4.3.3
v4.3.2Compare Source
What's Changed
@actions/artifactdependency to v2.1.5 and@actions/coreto v1.0.1 by @eggyhead in #562New Contributors
Full Changelog: actions/upload-artifact@v4.3.1...v4.3.2
v4.3.1Compare Source
v4.3.0Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4...v4.3.0
v4.2.0Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4...v4.2.0
v4.1.0Compare Source
What's Changed
New Contributors
Full Changelog: actions/upload-artifact@v4...v4.1.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.