-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
build: update CI file to lock actions and pass CI #196
base: main
Are you sure you want to change the base?
Conversation
df3724a
to
731f6d5
Compare
The in-range version of tmp-promise only supports node 14 and higher
Now includes CFA for auto-release 👍 |
os: [windows-latest, macOS-latest, ubuntu-latest] | ||
node-version: [10.x, 12.x] | ||
os: [windows-latest, macos-13, ubuntu-latest] | ||
node-version: [14.x, 16.x, 18.x, 20.x] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it overkill to include 22.x as well since that's LTS?
- name: Install | ||
run: | | ||
npm install --engine-strict | ||
npm update | ||
yarn install --frozen-lockfile --ignore-engines |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it intentional that we're keeping --ignore-engines
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah there's a testing dependency that declares it's node version range wrong. Still works clearly 😂
Also adds a lockfile because lock files are good.
Also turns out that despite the package claiming to support node 10/12, it did not due to the
tmp-promise
dependency. So I'm just being realistic and updating the min version to 14 to match reality. Tests are also added / passing now.