chore(ci): Bump actions/cache to v5 and actions/download-artifact to v7#20249
Open
chore(ci): Bump actions/cache to v5 and actions/download-artifact to v7#20249
Conversation
mydea
changed the title
Contributor
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨Core
Deps
Other
Bug Fixes 🐛Deno
Other
Internal Changes 🔧Ci
Deps
Other
🤖 This preview updates automatically when you update the PR. |
Contributor
size-limit report 📦
|
Contributor
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
mydea
changed the title
Upgrade `actions/cache/restore`, `actions/cache/save`, and `actions/download-artifact` from v4 to v5 in composite actions. Both v5 releases are non-breaking for our usage: - actions/cache v5: only upgrades Node.js runtime from 20 to 24, no input/output changes. - actions/download-artifact v5: the only breaking change is about downloads by artifact ID (nested directory behavior), which does not affect us since we download by name. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
download-artifact@v5 still runs on Node 20; v7 runs on Node 24 and aligns with actions/upload-artifact@v7 used in workflows. Co-Authored-By: Auto <noreply@anthropic.com> Made-with: Cursor
mydea
force-pushed
the
feat/bump-github-actions-v5
branch
from
81f9ebf to
1000cb7
Compare
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
1 participant
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.
Summary
actions/cache/restoreandactions/cache/savefrom v4 to v5 ininstall-playwrightandrestore-cachecomposite actionsactions/download-artifactfrom v4 to v7 inrestore-cachecomposite action (v5 still ran on Node 20; v7 runs on Node 24 and matchesactions/upload-artifact@v7elsewhere)Changelog
actions/cachev4 → v5actions/download-artifactv4 → v7runs.using: node24); v5 remained on Node 20, so it did not clear deprecation warnings for this stepactions/upload-artifact@v7already used in workflowsAffected files
.github/actions/install-playwright/action.yml—cache/restore@v4→v5,cache/save@v4→v5.github/actions/restore-cache/action.yml—cache/restore@v4→v5,download-artifact@v4→v7Test plan