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

Update dependency vitest to ~0.32.2 - autoclosed #27

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 1, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest ~0.26.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

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Berlin, 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 requested a review from Shinigami92 as a code owner January 1, 2023 17:37
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jan 1, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.26.3 Update dependency vitest to ~0.27.0 Jan 9, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.27.0 Update dependency vitest to ~0.27.1 Jan 11, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.27.1 Update dependency vitest to ~0.27.2 Jan 17, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.27.2 Update dependency vitest to ~0.27.3 Jan 21, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.27.3 Update dependency vitest to ~0.28.0 Jan 23, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.28.0 Update dependency vitest to ~0.28.1 Jan 23, 2023
@renovate renovate bot force-pushed the renovate/vitest branch 2 times, most recently from 09bd1ae to baa2fda Compare January 25, 2023 13:16
@renovate renovate bot changed the title Update dependency vitest to ~0.28.1 Update dependency vitest to ~0.28.2 Jan 25, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.28.2 Update dependency vitest to ~0.28.3 Jan 27, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.28.3 Update dependency vitest to ~0.28.4 Feb 3, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.28.4 Update dependency vitest to ~0.28.5 Feb 13, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.28.5 Update dependency vitest to ~0.29.3 Mar 16, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.29.3 Update dependency vitest to ~0.29.7 Mar 22, 2023
@renovate renovate bot force-pushed the renovate/vitest branch 2 times, most recently from d24b639 to f19f730 Compare March 28, 2023 13:22
@renovate renovate bot changed the title Update dependency vitest to ~0.29.7 Update dependency vitest to ~0.29.8 Mar 29, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.29.8 Update dependency vitest to ~0.30.1 Apr 17, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.30.1 Update dependency vitest to ~0.31.1 May 28, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.31.1 Update dependency vitest to ~0.31.2 May 30, 2023
@renovate renovate bot force-pushed the renovate/vitest branch 2 times, most recently from c585f6f to a81380e Compare May 31, 2023 17:07
@renovate renovate bot changed the title Update dependency vitest to ~0.31.2 Update dependency vitest to ~0.31.3 May 31, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.31.3 Update dependency vitest to ~0.31.4 Jun 2, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.31.4 Update dependency vitest to ~0.32.0 Jun 6, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.32.0 Update dependency vitest to ~0.32.1 Jun 16, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.32.1 Update dependency vitest to ~0.32.2 Jun 16, 2023
@renovate renovate bot changed the title Update dependency vitest to ~0.32.2 Update dependency vitest to ~0.32.2 - autoclosed Jun 17, 2023
@renovate renovate bot closed this Jun 17, 2023
@renovate renovate bot deleted the renovate/vitest branch June 17, 2023 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants