Skip to content

Conversation

slievrly
Copy link
Member

  • I have registered the PR changes.

Ⅰ. Describe what this PR did

upgrade outdated npmjs dependencies

Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

@slievrly slievrly added the Do Not Merge Do not merge into develop label Jun 26, 2025
Copy link

codecov bot commented Jun 26, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.32%. Comparing base (208c2cd) to head (0e38e4b).
⚠️ Report is 30 commits behind head on 2.x.

Additional details and impacted files
@@             Coverage Diff              @@
##                2.x    #7473      +/-   ##
============================================
+ Coverage     60.30%   60.32%   +0.02%     
  Complexity      658      658              
============================================
  Files          1281     1281              
  Lines         48281    48281              
  Branches       5676     5676              
============================================
+ Hits          29114    29125      +11     
+ Misses        16557    16546      -11     
  Partials       2610     2610              

see 5 files with indirect coverage changes

Impacted file tree graph

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Do Not Merge Do not merge into develop
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant