Skip to content

Upgrade to node16 #243

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 2 commits into from
Mar 2, 2023
Merged

Upgrade to node16 #243

merged 2 commits into from
Mar 2, 2023

Conversation

samwho
Copy link
Contributor

@samwho samwho commented Mar 2, 2023

GitHub have deprecated Node12 and plan to have all actions running on Node16 by summer 2023 (https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/).

This PR sets action.uses to node16, and also takes the liberty to upgrade the repo's own test workflow to actions/checkout@v3, as @v2 is also slated for deprecation. 🙂

I'm not sure what release process exists for this action, but I'm happy to help out further to get this released before the deadline.

@orgoro orgoro merged commit 6101373 into orgoro:main Mar 2, 2023
@orgoro
Copy link
Owner

orgoro commented Mar 2, 2023

Thanks @samwho

@samwho
Copy link
Contributor Author

samwho commented Mar 2, 2023

Hey @orgoro thanks for getting to this so quickly! I had noticed the CI run failed and was planning to look in to it after a few meetings, but you beat me to it. Any idea what the problem is? The error is a little cryptic. 😅

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.

2 participants