chore(deps): update github actions (major)#1612
Merged
Merged
Conversation
✅ Deploy Preview for viteplus-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
6bd786a to
113e0e9
Compare
Member
|
@claude[agent] keep |
Agent-Logs-Url: https://github.com/voidzero-dev/vite-plus/sessions/3c71ac81-b84a-40c0-a795-270f2d2fa329 Co-authored-by: Brooooooklyn <3468483+Brooooooklyn@users.noreply.github.com>
Contributor
Done in d9ad904 |
Brooooooklyn
approved these changes
May 18, 2026
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
fengmk2
approved these changes
May 18, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
v4.3.0→v8.0.122-alpine3.21→25-alpine3.21v5.0.0→v6.0.8v4.4.0→v6.0.8Release 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
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
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
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
nodejs/node (node)
v25Moved to doc/changelogs/CHANGELOG_V012.md#0.12.8.
v24Moved to doc/changelogs/CHANGELOG_IOJS.md#2.1.0.
v23Moved to doc/changelogs/CHANGELOG_V6.md#6.1.0.
pnpm/action-setup (pnpm/action-setup)
v6.0.8Compare Source
v6.0.7Compare Source
v6.0.6Compare Source
What's Changed
Full Changelog: pnpm/action-setup@v6.0.5...v6.0.6
v6.0.5Compare Source
What's Changed
Full Changelog: pnpm/action-setup@v6.0.4...v6.0.5
v6.0.4Compare Source
What's Changed
New Contributors
Full Changelog: pnpm/action-setup@v6.0.3...v6.0.4
v6.0.3Compare Source
Updated pnpm to v11.0.0-rc.5
Full Changelog: pnpm/action-setup@v6.0.2...v6.0.3
v6.0.2Compare Source
What's Changed
New Contributors
Full Changelog: pnpm/action-setup@v6.0.1...v6.0.2
v6.0.1Compare Source
Update pnpm to v11.0.0-rc.2.
pnpm-lock.yamlwill not be saved with two documents unless thepackageManageris set viadevEngines.packageManager. Related issue: #228v6.0.0Compare Source
Configuration
📅 Schedule: (in timezone Asia/Shanghai)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.