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

chore(deps): update vitest monorepo #86

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 1, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-c8 (source) 0.24.4 -> 0.33.0 age adoption passing confidence
vitest (source) 1.1.1 -> 1.5.2 age adoption passing confidence

Release Notes

vitest-dev/vitest (@​vitest/coverage-c8)

v0.33.0

Compare Source

   🚨 Breaking Changes
  • Revert default include patterns  -  by @​so1ve #​3729
    • 0.32.0 changed the default include globs to be compatible with Jest. After a discussion with the community, we are reverting this change because it turned out to be non-intuitive.
   🐞 Bug Fixes
    View changes on GitHub

v0.32.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.32.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.32.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.32.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.32.0

Compare Source

   🚨 Breaking Changes
  • Throw an error, if the module cannot be resolved  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3307 (1ad63)
    • Vitest used to fall back to the original import when it could not resolve it to the file path or the virtual module. This leads to hard-to-find module graph mismatches if you had incorrect alias or relied on relative imports to be resolved to the project root (which is usual behavior in TypeScript) because the code accidentally "worked". With this release, Vitest will now throw an error if it cannot resolve the module - there are possible edge cases that are not covered yet, so if you have any problems with this, please open a separate issue with reproduction.
  • Improve globs  -  by @​nickmccurdy in https://github.com/vitest-dev/vitest/issues/3392 (19ecc)
    • Vitest now has glob patterns similar to Jest for better compatibility. It's possible that some files will be considered test files when previously they were not. For example, Vitest now considers test.js to be a test file. Also any file in __tests__ is now considered to be a test, not just files with test or spec suffix.
  • Add @vitest/coverage-v8 package  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3339 (82112)
    • Vitest now uses v8 code coverage directly for better performance. @vitest/coverage-c8 is deprecated as Vitest no longer uses c8 package for coverage output. It will not be updated anymore, and Vitest will fail in the next version if the user has c8 as their coverage provider. Please, install the new @vitest/coverage-v8 package if you previously used @vitest/coverage-c8.
  • mocker: Don't restore mock to the original if the module is automocked  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3518 (c1004)
    • spy.mockRestore on auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does.
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.0

Compare Source

   🚨 Breaking Changes
  • Remove browser from allowed pools inside poolMatchGlob config option. Please, use Vitest workspaces for running tests in the browser.

  • Move assertion declarations to expect package  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3294 (cf3af)

    • The change should be minor:
    - declare namespace Vi {
    + declare module 'vitest' {
       interface Assertion<T = any> extends CustomMatchers<T> {}
       interface AsymmetricMatchersContaining extends CustomMatchers {}
    }
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.30.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.30.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.29.8

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.29.7

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.29.6

[Compare Source](https://togithub.com/vitest


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot enabled auto-merge (rebase) November 1, 2022 18:53
@codecov-commenter
Copy link

codecov-commenter commented Nov 1, 2022

Codecov Report

Merging #86 (620c170) into master (604d85c) will increase coverage by 0.47%.
The diff coverage is n/a.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@            Coverage Diff             @@
##           master      #86      +/-   ##
==========================================
+ Coverage   98.10%   98.58%   +0.47%     
==========================================
  Files           5        5              
  Lines         423      423              
  Branches      129      120       -9     
==========================================
+ Hits          415      417       +2     
+ Misses          8        6       -2     

see 2 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 47a8dd2 to 851fd98 Compare November 7, 2022 18:00
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.24.5 chore(deps): update vitest monorepo to v0.25.0 Nov 7, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from 5049a14 to 9932ae5 Compare November 8, 2022 18:51
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.25.0 chore(deps): update vitest monorepo to v0.25.1 Nov 8, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 1b18669 to 129ce49 Compare November 14, 2022 15:00
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.25.1 chore(deps): update vitest monorepo to v0.25.2 Nov 14, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 6 times, most recently from 962f3e8 to bf92b89 Compare November 21, 2022 20:19
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.25.2 chore(deps): update vitest monorepo to v0.25.3 Nov 22, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 5 times, most recently from dd635e4 to 3083868 Compare November 28, 2022 18:24
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 14599ef to 16b9293 Compare December 4, 2022 14:09
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 5 times, most recently from dacb173 to 5422e36 Compare March 21, 2024 03:43
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 947c290 to bbbce8e Compare March 30, 2024 10:33
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 7 times, most recently from ee66479 to 567490d Compare April 9, 2024 11:29
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 5 times, most recently from 2015d17 to 24da6c8 Compare April 14, 2024 12:03
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 9 times, most recently from 470585f to 2f6fa05 Compare April 26, 2024 10:03
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 2f6fa05 to a1820c0 Compare April 28, 2024 01:10
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