Skip to content

Update action cache version#44

Open
laetus007 wants to merge 1 commit intopantheon-systems:mainfrom
laetus007:feature/node-deprecations
Open

Update action cache version#44
laetus007 wants to merge 1 commit intopantheon-systems:mainfrom
laetus007:feature/node-deprecations

Conversation

@laetus007
Copy link
Copy Markdown

@laetus007 laetus007 commented Apr 2, 2026

We're updating our actions and this is the last one that still displays for us during our Github Action runs.

node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Our shop has us updating to the sha for security purposes so that is the decision here. I add the version number as an inline comment. Please note that this will need to be updated in 6 months or so when https://github.blog/news-insights/product-news/whats-coming-to-our-github-actions-2026-security-roadmap/ dependencies are fully rolled out.

Screenshot of deprecations

Screenshot 2026-04-02 at 6 58 09 AM

@laetus007 laetus007 requested a review from a team as a code owner April 2, 2026 13:12
@laetus007
Copy link
Copy Markdown
Author

Screenshot after running our workflow with this commit hash.

Screenshot 2026-04-02 at 6 56 19 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant