chore: repair lockfile and regenerate third-party notices#1423
Merged
Conversation
Contributor
Chrome DevTools Protocol Tracing (Script: 140.22ms, Heap: 11.67MB)
Lighthouse (Script Eval: 135.31ms)
Platform Tests (vite-7 es2015 gzip: 69.66KB)vite-6 Platform Tests
vite-7 Platform Tests
webpack-5 Platform Tests
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1423 +/- ##
==========================================
+ Coverage 96.67% 96.68% +0.01%
==========================================
Files 234 234
Lines 9918 9918
Branches 1381 1382 +1
==========================================
+ Hits 9588 9589 +1
+ Misses 328 327 -1
Partials 2 2 🚀 New features to boost your workflow:
|
jpmunz
approved these changes
Jul 10, 2026
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
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.
What problem is this solving?
The
package-lock.jsonhad drifted (largely around the commitlint / conventional-changelog toolchain), andTHIRD_PARTY_NOTICES.txtwas stale relative to the resolved dependency tree.Short description of changes
package-lock.json, deduping and cleaning up commitlint-related deps (conventional-changelog, git-raw-commits, meow, and transitive packages).THIRD_PARTY_NOTICES.txt(@opentelemetry/semantic-conventions1.41.1→1.42.0,import-in-the-middle3.3.0→3.3.1).How has this been tested?
npm installreconciles the lockfile cleanly andnpm run licensesreproduces the notices file. No source changes.Checklist