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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 6, 2023

This PR contains the following updates:

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

Configuration

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 6ae7a58 to 6872ff1 Compare June 12, 2023 21:13
@renovate renovate bot changed the title chore(deps): update vitest monorepo to ^0.32.0 chore(deps): update vitest monorepo to ^0.32.1 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 6872ff1 to 819fe60 Compare June 16, 2023 13:44
@renovate renovate bot changed the title chore(deps): update vitest monorepo to ^0.32.1 chore(deps): update vitest monorepo to ^0.32.2 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from d94fa40 to ba36db3 Compare June 19, 2023 21:40
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from fd8760b to 7ce0b34 Compare July 1, 2023 06:48
@renovate renovate bot changed the title chore(deps): update vitest monorepo to ^0.32.2 chore(deps): update vitest monorepo to ^0.32.3 Jul 3, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 7ce0b34 to bc60e72 Compare July 3, 2023 08:46
@renovate renovate bot changed the title chore(deps): update vitest monorepo to ^0.32.3 chore(deps): update vitest monorepo to ^0.32.4 Jul 3, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 5 times, most recently from 8eeb2ed to 86bf90a Compare July 6, 2023 04:29
@renovate renovate bot changed the title chore(deps): update vitest monorepo to ^0.32.4 chore(deps): update vitest monorepo to ^0.33.0 Jul 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 9 times, most recently from f54643c to 0f9e875 Compare July 13, 2023 03:48
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 12 times, most recently from b4572e2 to fd38a06 Compare March 27, 2024 05:02
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 7 times, most recently from 702af97 to 16dfb3b Compare April 5, 2024 05:07
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 6 times, most recently from 6b8d0c5 to 923aeff Compare April 10, 2024 20:41
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from 9c123fb to 7956731 Compare April 16, 2024 04:39
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 7956731 to 1c7ce72 Compare April 16, 2024 11:15
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.

0 participants