Conversation
There's a bug when running on node v22.10. This temporarily pins 22 to 22.9.0 to workaround the problem and keep tests passing on CI. Mitigation for issue #1180.
nfischer
force-pushed
the
chore-pin-node-22
branch
from
37f7fa0 to
93909ce
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1182 +/- ##
=======================================
Coverage 97.28% 97.28%
=======================================
Files 36 36
Lines 1361 1361
=======================================
Hits 1324 1324
Misses 37 37 ☔ View full report in Codecov by Sentry. |
kmashint
approved these changes
Feb 15, 2025
Contributor
kmashint
left a comment
kmashint
left a comment
There was a problem hiding this comment.
Worked for the cloud builds.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
There's a bug when running on node v22.10. This temporarily pins 22 to 22.9.0 to workaround the problem and keep tests passing on CI.
Mitigation for issue #1180.