test: pin prisma to < 5 when running on node 14 #1717
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
Codecov Report
@@ Coverage Diff @@
## main #1717 +/- ##
==========================================
- Coverage 96.87% 91.46% -5.41%
==========================================
Files 200 179 -21
Lines 39181 37073 -2108
Branches 24 0 -24
==========================================
- Hits 37956 33910 -4046
- Misses 1225 3163 +1938
Flags with carried forward coverage won't be shown. Click here to find out more. see 84 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
jmartin4563
approved these changes
Jul 12, 2023
Merged
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.
Description
Prisma dropped Node 14 in version 5. Until we drop 14, we need to prevent our versioned tests from running >=5 on Node 14. #1715 is also testing if the instrumentation crashes and if we have to do a semver check in instrumentation. This is just to unblock CI.