Skip to content

fix(ci): upgrade actions/setup-node@v2 to v4 #477

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 7, 2025
Merged

Conversation

ezolenko
Copy link
Owner

@ezolenko ezolenko commented May 7, 2025

Summary

actions/setup-node@v2 was deprecated

actions/setup-node#1275

Details

Updating to v4

@ezolenko ezolenko merged commit 8743691 into master May 7, 2025
6 checks passed
@ezolenko ezolenko deleted the workflows_fix branch May 7, 2025 16:38
@ezolenko
Copy link
Owner Author

ezolenko commented May 7, 2025

@agilgur5 FYI

@agilgur5
Copy link
Collaborator

agilgur5 commented May 8, 2025

Thanks ezolenko! I suspected there might be an update to CI needed for the failed CI runs of #476, but hadn't investigated it yet.

For posterity, the error is equivalent to the one described in actions/setup-node#1275, where this contributor comment says to update from actions/setup-node@v2 to v4 due to an actions/cache change (per the linked actions/toolkit#1890). That's exactly what you did here, which did indeed fix CI.

@agilgur5 agilgur5 added kind: bug Something isn't working properly scope: dependencies Issues or PRs about updating a dependency kind: internal Changes only affect the internals, and _not_ the public API or external-facing docs labels May 8, 2025
@agilgur5 agilgur5 changed the title actions/setup-node@v2 to v4 fix(ci): upgrade actions/setup-node@v2 to v4 May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: bug Something isn't working properly kind: internal Changes only affect the internals, and _not_ the public API or external-facing docs scope: dependencies Issues or PRs about updating a dependency
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants