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 #37

Merged
merged 1 commit into from
Oct 10, 2023
Merged

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 29, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-c8 (source) 0.29.2 -> 0.33.0 age adoption passing confidence
vitest 0.29.2 -> 0.34.6 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-dev/vitest/co


Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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.

@codecov
Copy link

codecov bot commented May 29, 2023

Codecov Report

Merging #37 (20bbd12) into main (2dde65c) will not change coverage.
Report is 18 commits behind head on main.
The diff coverage is n/a.

❗ Current head 20bbd12 differs from pull request most recent head 6be3efc. Consider uploading reports for the commit 6be3efc to get more accurate results

@@            Coverage Diff            @@
##              main       #37   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines            9         9           
  Branches         5         4    -1     
=========================================
  Hits             9         9           

@renovate renovate bot changed the title Update vitest monorepo to v0.31.1 Update vitest monorepo to v0.31.2 May 30, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b716b71 to 53a0e0e Compare May 30, 2023 15:58
@renovate renovate bot changed the title Update vitest monorepo to v0.31.2 Update vitest monorepo to v0.31.3 May 31, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 53a0e0e to c324ea9 Compare May 31, 2023 15:27
@renovate renovate bot changed the title Update vitest monorepo to v0.31.3 Update vitest monorepo to v0.31.4 Jun 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from c324ea9 to 20bbd12 Compare June 1, 2023 11:29
@renovate renovate bot changed the title Update vitest monorepo to v0.31.4 Update vitest monorepo to v0.32.0 Jun 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 20bbd12 to eb21d21 Compare June 6, 2023 17:57
@renovate renovate bot changed the title Update vitest monorepo to v0.32.0 Update vitest monorepo to v0.32.1 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from f0ca92a to c4aff28 Compare June 16, 2023 19:21
@renovate renovate bot changed the title Update vitest monorepo to v0.32.1 Update vitest monorepo to v0.32.2 Jun 16, 2023
@renovate renovate bot changed the title Update vitest monorepo to v0.32.2 chore(deps): update vitest monorepo to v0.32.2 Jun 29, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from c4aff28 to 24654be Compare June 29, 2023 17:12
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.32.2 chore(deps): update vitest monorepo to v0.32.4 Jul 3, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 24654be to 53118cf Compare July 3, 2023 11:26
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.32.4 chore(deps): update vitest monorepo to v0.33.0 Jul 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 53118cf to d0b01f3 Compare July 6, 2023 15:51
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d0b01f3 to dcad43c Compare August 1, 2023 16:33
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.33.0 chore(deps): update vitest monorepo Aug 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from dcad43c to 0251205 Compare August 1, 2023 19:47
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 0251205 to 581290b Compare August 17, 2023 11:35
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 581290b to aa17d42 Compare August 25, 2023 10:38
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from aa17d42 to 1ac65ed Compare September 8, 2023 11:26
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 1ac65ed to 429245d Compare September 21, 2023 16:08
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 429245d to b90c1fa Compare September 29, 2023 12:15
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b90c1fa to fd06223 Compare October 10, 2023 17:14
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from fd06223 to 6be3efc Compare October 10, 2023 17:20
@jamacku jamacku merged commit bae4762 into main Oct 10, 2023
5 of 7 checks passed
@renovate renovate bot deleted the renovate/vitest-monorepo branch October 10, 2023 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant