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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 1, 2023

Mend Renovate

This PR contains the following updates:

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

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), 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.

👻 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 4 times, most recently from 1363447 to 713fe87 Compare October 5, 2023 06:58
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 713fe87 to 835cc15 Compare October 5, 2023 06:59
@jamacku jamacku force-pushed the renovate/vitest-monorepo branch from 835cc15 to 79a8909 Compare October 5, 2023 07:03
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 79a8909 to 1cea6f0 Compare October 5, 2023 07:03
@codecov
Copy link

codecov bot commented Oct 5, 2023

Codecov Report

Merging #53 (0e28420) into main (b3e6ef2) will increase coverage by 0.25%.
The diff coverage is n/a.

❗ Current head 0e28420 differs from pull request most recent head b4ae9a9. Consider uploading reports for the commit b4ae9a9 to get more accurate results

@@            Coverage Diff             @@
##             main      #53      +/-   ##
==========================================
+ Coverage   98.47%   98.72%   +0.25%     
==========================================
  Files           4        4              
  Lines         393      393              
  Branches       41       30      -11     
==========================================
+ Hits          387      388       +1     
+ Misses          6        5       -1     

see 1 file with indirect coverage changes

@jamacku jamacku force-pushed the renovate/vitest-monorepo branch from 1cea6f0 to 0e28420 Compare October 5, 2023 07:11
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 0e28420 to 12f1083 Compare October 5, 2023 07:11
@jamacku jamacku enabled auto-merge (rebase) October 5, 2023 07:12
@jamacku jamacku disabled auto-merge October 5, 2023 07:13
@jamacku jamacku force-pushed the renovate/vitest-monorepo branch from 12f1083 to 0e28420 Compare October 5, 2023 07:14
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 0e28420 to b4ae9a9 Compare October 5, 2023 07:14
@renovate renovate bot changed the title chore(deps): update vitest monorepo chore(deps): update vitest monorepo - autoclosed Oct 6, 2023
@renovate renovate bot closed this Oct 6, 2023
@renovate renovate bot deleted the renovate/vitest-monorepo branch October 6, 2023 07:10
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.

1 participant