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

test: remove Node.js 10 and 12 from CI #1477

Merged
merged 3 commits into from Mar 15, 2023
Merged

test: remove Node.js 10 and 12 from CI #1477

merged 3 commits into from Mar 15, 2023

Conversation

ludofischer
Copy link
Collaborator

Remove unmaintained Node.js from CI. As we're not testing against Node.js 10 and 12 I think we need to bump the minimal supported Node version on all packages, because we cannot guarantee that we won't introduce an incompatibility in the future.

@codecov-commenter
Copy link

Codecov Report

Patch and project coverage have no change.

Comparison is base (4e272f8) 97.62% compared to head (e5f5192) 97.62%.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1477   +/-   ##
=======================================
  Coverage   97.62%   97.62%           
=======================================
  Files         122      122           
  Lines       10000    10000           
=======================================
  Hits         9762     9762           
  Misses        238      238           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@ludofischer
Copy link
Collaborator Author

@alexander-akait I think you need to update the required checks on master if we want to get rid of the Node.js 10 and 12 tests because I haven't got access to that setting.

@alexander-akait
Copy link
Member

WIP

@alexander-akait
Copy link
Member

Done 👍

@ludofischer
Copy link
Collaborator Author

WIP

Are you sure you want to make 19 required? Then we'll need to change the settings again in June when it becomes EOL and replaced by 20.

@ludofischer ludofischer merged commit ca9d3f5 into master Mar 15, 2023
@ludofischer ludofischer deleted the adjust-versions branch March 15, 2023 21:46
@alexander-akait
Copy link
Member

On the one hand, I agree that this is not necessary, on the other hand, we can catch all potential compatibility gaps (to be honest, I don’t think they will, but I have met very different situations), so let's keep it, if we will need to do release rapidly, we can ignore it and merge

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

3 participants