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

Upgrade to Node 16 #82

Closed
wants to merge 9 commits into from

Conversation

evgenyrahman
Copy link

@evgenyrahman evgenyrahman commented Mar 9, 2023

Background

GitHub Actions is deprecating support for Node 12 support as Node 12 has gone out of support

This pull request updates action.yml and dependency-related files for this Action to use Node 16 in line with GitHub recommendations

Testing

I changed one of my projects to use the updated version of the Action from my forked repo and ran the workflow that uses it, and the workflow completed successfully.

Todos

  • Update README.md with instructions for setting export NODE_OPTIONS=--openssl-legacy-provider to solve the ERR_OSSL_EVP_UNSUPPORTED build-time error.

@evgenyrahman evgenyrahman marked this pull request as ready for review March 9, 2023 19:21
README.md Outdated
1. `npm run dist` and commit the built output (yes, you read that right)
2. Bump whatever you want to bump in the `package.json` version field
3. Merge `main` into `vMAJOR` branch. `git checkout vMAJOR && git merge main`
1. Set the `NODE_OPTIONS` environment variale to `--openssl-legacy-provider`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

might it make more sense to bake this into the dist command? https://github.com/githubocto/flat/blob/main/package.json#LL10C14-L10C14

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes! I will update and test.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Wattenberger updated!

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like this will require a little more work than I thought as Node versions 16 and lower do not like setting the --openssl-legacy-provider in NODE_OPTIONS

@@ -0,0 +1,93 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any idea why this adds a package.json file to the dist folder?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure! I will check across revisions and see what causes this.

@evgenyrahman
Copy link
Author

Still working on this!

@mattrothenberg
Copy link
Contributor

Closing in favor of #86

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.

3 participants