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

Merged
merged 1 commit into from
Aug 29, 2023
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 30, 2023

Mend Renovate

This PR contains the following updates:

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

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.

👻 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 changed the title chore(deps): update vitest monorepo to v0.31.2 chore(deps): update vitest monorepo to v0.31.3 May 31, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 1798e9d to 9702892 Compare May 31, 2023 15:39
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.31.3 chore(deps): update vitest monorepo to v0.31.4 Jun 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 5d68633 to 1d79010 Compare June 4, 2023 11:33
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.31.4 chore(deps): update vitest monorepo to ^0.32.0 Jun 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 1d79010 to 671c8d4 Compare June 6, 2023 17:23
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 671c8d4 to 9ce57aa Compare June 16, 2023 17:09
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 9ce57aa to 2079584 Compare July 3, 2023 11:51
@renovate renovate bot changed the title chore(deps): update vitest monorepo to ^0.32.0 chore(deps): update vitest monorepo to ^0.33.0 Jul 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 2079584 to 19e5727 Compare July 6, 2023 18:02
@renovate renovate bot changed the title chore(deps): update vitest monorepo to ^0.33.0 chore(deps): update vitest monorepo Aug 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 19e5727 to 08e4f01 Compare August 1, 2023 18:07
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 08e4f01 to c0110aa Compare August 17, 2023 14:21
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from 982ce74 to 0f36d84 Compare August 29, 2023 12:04
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 0f36d84 to f0bc49c Compare August 29, 2023 12:08
@hwbllmnn hwbllmnn merged commit 2cce7f1 into master Aug 29, 2023
4 checks passed
@hwbllmnn hwbllmnn deleted the renovate/vitest-monorepo branch August 29, 2023 12:13
@dnlkoch
Copy link
Contributor

dnlkoch commented Dec 4, 2023

🎉 This PR is included in version 5.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants