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: update dependency vitest to v0.32.2 - autoclosed #688

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 24, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest 0.27.2 -> 0.32.2 age adoption passing confidence

Release Notes

vitest-dev/vitest

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

   🐞 Bug Fixes
    View changes on GitHub

v0.29.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.29.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.29.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v0.29.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.29.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.29.0

Compare Source

This release makes some significant changes to how tests are running. If you were using --no-threads before, you might consider enabling --single-thread instead (because your tests are now running in child_process instead of a worker thread) or try our new performance optimization feature (discussed later). If you were relying on API that was not available inside a worker (like process.chdir(), you can now use this option.

One of the potential breaking bug fixes is that environments do not share the same global scope anymore if you run them with --no-isolate, --no-threads or --single-thread - you might need to update your setup files if you were relying on a global variable before.

If you had performance issues on large code bases before, try the new deps.experimentalOptimizer option instead of disabling threads. Feedback is welcome!

One of the breaking changes includes adding a link to snapshots inside snapshot files, meaning you will need to update all your snapshots.

   🚨 Breaking Changes
  • Vitest as peer dependency for coverage packages  -  by [@​AriPerkkio](https://togi

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • 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 6 times, most recently from ababdaa to 94598db Compare February 28, 2023 09:15
@renovate renovate bot changed the title chore: update dependency vitest to v0.28.5 chore: update dependency vitest to v0.29.0 Feb 28, 2023
@renovate renovate bot changed the title chore: update dependency vitest to v0.29.0 chore: update dependency vitest to v0.29.1 Feb 28, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from bac9224 to 331efb3 Compare March 4, 2023 01:40
@renovate renovate bot changed the title chore: update dependency vitest to v0.29.1 chore: update dependency vitest to v0.29.2 Mar 4, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 331efb3 to 7f1777b Compare March 7, 2023 23:55
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 7f1777b to 6df9c3b Compare March 18, 2023 20:22
@renovate renovate bot changed the title chore: update dependency vitest to v0.29.2 chore: update dependency vitest to v0.29.3 Mar 18, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 9ec4b64 to 73d6c53 Compare March 23, 2023 14:30
@renovate renovate bot changed the title chore: update dependency vitest to v0.29.3 chore: update dependency vitest to v0.29.5 Mar 23, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 73d6c53 to 144f2db Compare March 23, 2023 20:42
@renovate renovate bot changed the title chore: update dependency vitest to v0.29.5 chore: update dependency vitest to v0.29.7 Mar 23, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 144f2db to eb4bd99 Compare March 31, 2023 17:20
@renovate renovate bot changed the title chore: update dependency vitest to v0.29.7 chore: update dependency vitest to v0.29.8 Mar 31, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from eb4bd99 to 14511cc Compare April 12, 2023 14:44
@renovate renovate bot changed the title chore: update dependency vitest to v0.29.8 chore: update dependency vitest to v0.30.0 Apr 12, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 14511cc to 7cd73fa Compare April 14, 2023 15:47
@renovate renovate bot changed the title chore: update dependency vitest to v0.30.0 chore: update dependency vitest to v0.30.1 Apr 14, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from b408e81 to b894c00 Compare April 26, 2023 16:48
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b894c00 to 06686fc Compare May 6, 2023 18:43
@renovate renovate bot changed the title chore: update dependency vitest to v0.30.1 chore: update dependency vitest to v0.31.0 May 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 06686fc to 18b4bd7 Compare May 20, 2023 15:38
@renovate renovate bot changed the title chore: update dependency vitest to v0.31.0 chore: update dependency vitest to v0.31.1 May 20, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 18b4bd7 to e06a899 Compare June 2, 2023 13:35
@renovate renovate bot changed the title chore: update dependency vitest to v0.31.1 chore: update dependency vitest to v0.31.2 Jun 2, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e06a899 to f331ce1 Compare June 3, 2023 15:17
@renovate renovate bot changed the title chore: update dependency vitest to v0.31.2 chore: update dependency vitest to v0.31.3 Jun 3, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from f331ce1 to aa1422d Compare June 4, 2023 13:19
@renovate renovate bot changed the title chore: update dependency vitest to v0.31.3 chore: update dependency vitest to v0.31.4 Jun 4, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 6 times, most recently from 7daca5f to d36c4e5 Compare June 9, 2023 18:57
@renovate renovate bot changed the title chore: update dependency vitest to v0.31.4 chore: update dependency vitest to v0.32.0 Jun 9, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 6 times, most recently from bccb293 to 02c1ab6 Compare June 19, 2023 12:33
@renovate renovate bot changed the title chore: update dependency vitest to v0.32.0 chore: update dependency vitest to v0.32.1 Jun 19, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 02c1ab6 to 824c34d Compare June 19, 2023 18:01
@renovate renovate bot changed the title chore: update dependency vitest to v0.32.1 chore: update dependency vitest to v0.32.2 Jun 19, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 824c34d to ed2d9ff Compare June 24, 2023 03:38
@renovate renovate bot changed the title chore: update dependency vitest to v0.32.2 chore: update dependency vitest to v0.32.2 - autoclosed Jun 25, 2023
@renovate renovate bot closed this Jun 25, 2023
@renovate renovate bot deleted the renovate/vitest-monorepo branch June 25, 2023 13:43
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.

None yet

0 participants