fix(deps): regenerate package-lock.json#2862
Conversation
Co-Authored-By: Claude Code <noreply@anthropic.com>
|
@brian-smith-tcril Wow that's a lot of changes to the lockfile. More deletions than additions is good, but it still seems like it shouldn't be that different? |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2862 +/- ##
=======================================
Coverage 95.18% 95.18%
=======================================
Files 1319 1319
Lines 30022 30022
Branches 6754 6771 +17
=======================================
Hits 28575 28575
Misses 1378 1378
Partials 69 69 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
bradenmacdonald
left a comment
There was a problem hiding this comment.
OK, I guess there's just a lot of minor version bumps, as well as better de-duplication of jest. This looks great!
I clicked around for some smoke tests and didn't see any issues. Running npm install locally generated only one peer: true line changed in package-lock.json which is a super minor discrepancy that we can fix later.
Renovate can't seem to handle the changes needed for #2843
Regenerating the lockfile works.
What I ran to regenerate the lockfile:
This PR was created by Claude Code. See the plan for details.