- Notifications
You must be signed in to change notification settings - Fork 949
chore: use lockfile version 3 #5978
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
chore: use lockfile version 3 #5978
Conversation
3f3780c to 429f0a7 Compare 429f0a7 to b94bc86 Compare Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@ ## main #5978 +/- ## ======================================= Coverage 95.17% 95.17% ======================================= Files 316 316 Lines 8521 8521 Branches 1763 1763 ======================================= Hits 8110 8110 Misses 411 411 🚀 New features to boost your workflow:
|
| I might have spent a lot of time working through issues on this PR that are likely somehow related to npm/cli#8628. Some optional dependencies did not get installed that used to be there before (like the ones on |
| not sure what's going on with windows tests though. I'll try making out CI use |
| Opened #5979 to pin to |
ecf5137 to da07a46 Compare 0864ddf to d25de88 Compare
Which problem is this PR solving?
Same as the PR in contrib: open-telemetry/opentelemetry-js-contrib#3117
Bumped to
lockfile-version=3, regenerated thepackage-lock.jsonI suspect that this will fix the issues in #5976