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 dependency @vitest/coverage-c8 to ^0.33.0 - autoclosed #125

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 12, 2023

Mend Renovate

This PR contains the following updates:

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

Configuration

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

🚦 Automerge: Enabled.

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 added the dependencies Pull requests that update a dependency file label Apr 12, 2023
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Issue Reference

In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide. We are closing this pull request for now but you can update the pull request description and reopen the pull request.
The check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.

@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 2 times, most recently from 1765879 to e040c43 Compare April 16, 2023 04:32
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 2 times, most recently from 322e01e to 9256e65 Compare April 22, 2023 20:00
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 2 times, most recently from c6d8f42 to f6521e8 Compare May 6, 2023 19:31
@renovate renovate bot changed the title chore(deps): update dependency @vitest/coverage-c8 to ^0.30.0 chore(deps): update dependency @vitest/coverage-c8 to ^0.31.0 May 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 2 times, most recently from 9ee6b77 to deac8e6 Compare May 10, 2023 21:39
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 3 times, most recently from a249d96 to 6be8744 Compare June 3, 2023 15:14
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 3 times, most recently from cb33a2c to 8edfb70 Compare June 9, 2023 17:40
@renovate renovate bot changed the title chore(deps): update dependency @vitest/coverage-c8 to ^0.31.0 chore(deps): update dependency @vitest/coverage-c8 to ^0.32.0 Jun 9, 2023
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 4 times, most recently from ece4687 to 7069943 Compare June 18, 2023 18:40
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 4 times, most recently from 10fc9b6 to c785f6a Compare June 29, 2023 13:10
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 3 times, most recently from 1049b5f to 3153fd3 Compare July 9, 2023 15:51
@renovate renovate bot changed the title chore(deps): update dependency @vitest/coverage-c8 to ^0.32.0 chore(deps): update dependency @vitest/coverage-c8 to ^0.33.0 Jul 9, 2023
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch from 3153fd3 to 6d6d7a4 Compare July 13, 2023 04:42
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 4 times, most recently from 8df706a to 82fe532 Compare July 27, 2023 03:24
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 3 times, most recently from e346a54 to d285e33 Compare August 9, 2023 16:48
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch from d285e33 to 8cb3b82 Compare August 12, 2023 22:32
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 3 times, most recently from 1eec066 to 42eab54 Compare September 3, 2023 18:04
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 4 times, most recently from 4ee7917 to b0363f7 Compare October 24, 2023 04:11
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 3 times, most recently from 5c65e57 to 78e96e3 Compare November 11, 2023 04:01
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch 2 times, most recently from 9a92318 to 7d53ad6 Compare February 16, 2024 07:07
@renovate renovate bot force-pushed the renovate/vitest-coverage-c8-0.x branch from 7d53ad6 to de9ec9f Compare February 16, 2024 09:47
@renovate renovate bot enabled auto-merge (squash) March 27, 2024 21:06
@renovate renovate bot changed the title chore(deps): update dependency @vitest/coverage-c8 to ^0.33.0 chore(deps): update dependency @vitest/coverage-c8 to ^0.33.0 - autoclosed Mar 28, 2024
@renovate renovate bot closed this Mar 28, 2024
auto-merge was automatically disabled March 28, 2024 14:57

Pull request was closed

@renovate renovate bot deleted the renovate/vitest-coverage-c8-0.x branch March 28, 2024 14:57
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.

0 participants