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

upgrading vitest to 2.0.5 #270

Merged
merged 3 commits into from
Aug 30, 2024
Merged

upgrading vitest to 2.0.5 #270

merged 3 commits into from
Aug 30, 2024

Conversation

jaredwray
Copy link
Owner

@jaredwray jaredwray commented Aug 30, 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, ...)
upgrading vitest to 2.0.5

Copy link

codecov bot commented Aug 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (06b742c) to head (98db031).
Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #270   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines          154       111   -43     
  Branches        21        21           
=========================================
- Hits           154       111   -43     

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

@jaredwray jaredwray merged commit c8bb615 into main Aug 30, 2024
7 checks passed
@jaredwray jaredwray deleted the upgrading-vitest-to-2.0.5 branch August 30, 2024 16:39
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.

1 participant