Skip to content
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

mono - upgrading vitest to 1.6.0 #1053

Merged
merged 2 commits into from
May 11, 2024
Merged

Conversation

jaredwray
Copy link
Owner

@jaredwray jaredwray commented May 11, 2024

Please check if the PR fulfills these requirements

  • Followed the Contributing guidelines.
  • Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
mono - upgrading vitest to 1.6.0

Copy link

codecov bot commented May 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.79%. Comparing base (52c125e) to head (de52a3a).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1053      +/-   ##
==========================================
- Coverage   99.80%   99.79%   -0.01%     
==========================================
  Files          40       40              
  Lines        3000     2999       -1     
  Branches      584      588       +4     
==========================================
- Hits         2994     2993       -1     
  Misses          5        5              
  Partials        1        1              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jaredwray jaredwray merged commit 38acb4b into main May 11, 2024
7 checks passed
@jaredwray jaredwray deleted the mono---upgrading-vitest-to-1.6.0 branch May 11, 2024 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant