Skip to content

Conversation

@cbnuLeehyunwoo
Copy link
Contributor

@cbnuLeehyunwoo cbnuLeehyunwoo commented Jun 4, 2025

This PR updates the CI workflow to use actions/setup-node@v3 instead of v2, as a preventive measure against potential cache restore failures.

While no error has occurred yet, recent changes in GitHub Actions caching infrastructure suggest that workflows relying on deprecated versions of actions/cache (used internally by setup-node@v2)
Relevant discussions:

actions/setup-node#1275

actions/toolkit/discussions/1890

if there’s a better approach or refinements needed, I’m happy to revise or close the PR as needed.

Thank you for your time and consideration!

Related Issue
Closes #728

@ashmaroli
Copy link
Member

Hello @cbnuLeehyunwoo.
Thank you for submitting this pull request.

Lets upgrade to v4 of action now. We shall consider downgrading if and when some issue props up in the future.

@cbnuLeehyunwoo
Copy link
Contributor Author

Thanks for the review! @ashmaroli
Sure — I’ll update this PR to use setup-node@v4 as suggested.

@cbnuLeehyunwoo cbnuLeehyunwoo changed the title Prevent Cache Issues by Upgrading setup-node to v3 Prevent Cache Issues by Upgrading setup-node@v2 to v3 or v4 Jun 4, 2025
@cbnuLeehyunwoo cbnuLeehyunwoo changed the title Prevent Cache Issues by Upgrading setup-node@v2 to v3 or v4 Prevent Cache Issues by Upgrading setup-node@v2 to @v4 Jun 4, 2025
@ashmaroli ashmaroli changed the title Prevent Cache Issues by Upgrading setup-node@v2 to @v4 Bump setup-node action to v4 Jun 5, 2025
@ashmaroli
Copy link
Member

Thank you @cbnuLeehyunwoo

@ashmaroli ashmaroli merged commit d29003e into jekyll:master Jun 5, 2025
7 checks passed
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.

CI Workflow: actions/setup-node@v2 is encountering a cache Error(getCacheEntry failed), due to actions/cache Deprecation

2 participants