Skip to content
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

Temporarily disabled cache usage for v2 #308

Merged
merged 3 commits into from Aug 3, 2021

Conversation

AlenaSviridenko
Copy link
Contributor

@AlenaSviridenko AlenaSviridenko commented Aug 3, 2021

Temporarily disabling usage of pre-cached Node.js versions

@AlenaSviridenko AlenaSviridenko merged commit d6e3b55 into main Aug 3, 2021
94 checks passed
@HonkingGoose
Copy link
Contributor

HonkingGoose commented Aug 3, 2021

Temporarily disabling usage of pre-cached Node.js versions

I just got a Renovate bot PR that wants to update action/setup-node from v2.3.0 to v2.3.1, and I'm really confused on why I as a end-user should update to the newer version.

Can somebody explain in a general sense what's going wrong right now, and how the temporary fix helps with this problem?

I've read the PR description, and checked the latest release notes, but they don't have a explanation at all.

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.

None yet

3 participants