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

feat!: drop node 12 support for plugin execution #4741

Merged

Conversation

lukasholzer
Copy link
Contributor

@lukasholzer lukasholzer commented Dec 5, 2022

πŸŽ‰ Thanks for submitting a pull request! πŸŽ‰

Summary

Fixes https://github.com/netlify/pillar-workflow/issues/955

Doing the node 12 support drop for the plugins execution based on our forums announcement.
See more details here: https://www.notion.so/netlify/Node-Versions-with-Plugins-55e9c5eb9c5f48d88c2f5925d9035b28

follow up based on: https://github.com/netlify/pillar-workflow/issues/968

cc @kitop @gualterandre @fool


For us to review and ship your PR efficiently, please perform the following steps:

  • Open a bug/issue before writing your code πŸ§‘β€πŸ’». This ensures
    we can discuss the changes and get feedback from everyone that should be involved. If you`re fixing a typo or
    something that`s on fire πŸ”₯ (e.g. incident related), you can skip this step.
  • Read the contribution guidelines πŸ“–. This ensures your code follows our style guide and
    passes our tests.
  • Update or add tests (if any source code was changed or added) πŸ§ͺ
  • Update or add documentation (if features were changed or added) πŸ“
  • Make sure the status checks below are successful βœ…

A picture of a cute animal (not mandatory, but encouraged)

/**
* @deprecated will be replaced with `MINIMUM_REQUIRED_NODE_VERSION` at the 5th. of December 2022
*/
const OLD_MINIMUM_REQUIRED_NODE_VERSION = '^12.20.0 || ^14.14.0 || >=16.0.0'
/**
* This node version is minimum required to run the plugins code.
* If the users preferred Node.js version is below that we have to fall back to the system node version
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's hope that everything works, as everywhere we dropped < 4.16 but here we allow >= 4.14. I know why we did this, but just saying this is something we should keep an eye on.

Copy link
Contributor

@danez danez left a comment

Choose a reason for hiding this comment

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

lgtm code wise

@danez
Copy link
Contributor

danez commented Dec 5, 2022

Should we have a FF to turn this on/off just to be safe?

@lukasholzer
Copy link
Contributor Author

Should we have a FF to turn this on/off just to be safe?

I think this is not necessary as we communicated this change upfront and support reached out to individual customers about that.

Would be off if we then revert it once we released it.

@lukasholzer lukasholzer merged commit c8d5a5e into main Dec 5, 2022
@lukasholzer lukasholzer deleted the feat/dropping-node-12-support-for-plugin-execution branch December 5, 2022 13:09
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

2 participants