chore: remove unsupported node configs from CI #221
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nfischer
force-pushed
the
chore-drop-node-v12
branch
from
19a6f4c
to
a3104ff
Compare
No change to logic. GitHub Actions recently dropped some NodeJS configurations from their service. This excludes those configs from our CI. This also adds Node versions up through v22. Test: npm run check-node-support
nfischer
force-pushed
the
chore-drop-node-v12
branch
from
a3104ff
to
e50fe19
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #221 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 5 5
Lines 114 114
=========================================
Hits 114 114 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No change to logic. GitHub Actions recently dropped some NodeJS
configurations from their service. This excludes those configs from our
CI.
This also adds Node versions up through v22.
Test: npm run check-node-support