-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Drop engines restriction #7804
Drop engines restriction #7804
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🦋 Changeset detectedLatest commit: a3d81a7 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit a3d81a7:
|
Fixes
I don't think we need to be opinionated about this, if our dependencies have a node requirement, that can be followed up with them. The prescriptive approach isn't exactly helpful.
We continue to test against the changing
lts/*
versions of Node year-on-year, and now demark that in our README, we are doing the responsible thing.keystone/.github/actions/ci-setup/action.yml
Line 8 in c0165f3
TODO
lts/*
only support