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 - autoclosed #320

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 28, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-c8 (source) 0.27.3 -> 0.33.0 age adoption passing confidence
@vitest/ui (source) ^0.27.2 -> ^0.34.0 age adoption passing confidence
vitest (source) 0.27.3 -> 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

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,every weekend,before 5am every weekday" (UTC), 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 force-pushed the renovate/vitest-monorepo branch from 24577d5 to 5e08d3e Compare April 9, 2023 14:41
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.29.8 chore(deps): update vitest monorepo to v0.30.0 Apr 9, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 5e08d3e to 2b6a16d Compare April 11, 2023 14:16
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.30.0 chore(deps): update vitest monorepo to v0.30.1 Apr 11, 2023
@github-actions
Copy link

github-actions bot commented Apr 11, 2023

Test Results

0 tests   - 309   0 ✔️  - 309   0s ⏱️ -2s
0 suites  -   47   0 💤 ±    0 
0 files    -     1   0 ±    0 

Results for commit 9ba797c. ± Comparison against base commit 9e0c68d.

♻️ This comment has been updated with latest results.

@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.30.1 chore(deps): update vitest monorepo to v0.31.0 May 3, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 2b6a16d to 43f248e Compare May 3, 2023 19:31
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.31.0 chore(deps): update vitest monorepo to v0.31.1 May 28, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 4924af8 to 5eba16f Compare June 1, 2023 16:29
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.31.1 chore(deps): update vitest monorepo to v0.31.4 Jun 1, 2023
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.31.4 chore(deps): update vitest monorepo to v0.32.0 Jun 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from b081b61 to fb5cb38 Compare June 11, 2023 10:19
@renovate
Copy link
Contributor Author

renovate bot commented Jun 11, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@meza meza changed the base branch from next to main June 11, 2023 11:04
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 7 times, most recently from 9501728 to 0c99130 Compare June 16, 2023 03:13
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.32.0 chore(deps): 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 b18b08a to 05474d7 Compare June 16, 2023 19:50
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.32.1 chore(deps): update vitest monorepo to v0.32.2 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 668ec2a to 45c967a Compare June 17, 2023 04:39
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 9 times, most recently from 0f274c2 to fd5f935 Compare December 2, 2023 00:26
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 16 times, most recently from 6c91c06 to 2164c89 Compare December 12, 2023 01:07
@renovate renovate bot changed the title chore(deps): update vitest monorepo chore(deps): update vitest monorepo - autoclosed Dec 12, 2023
@renovate renovate bot closed this Dec 12, 2023
@renovate renovate bot deleted the renovate/vitest-monorepo branch December 12, 2023 17:54
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

0 participants