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 to ^0.34.0 - autoclosed #231

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 12, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) ^0.29.0 -> ^0.34.0 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

v0.34.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.34.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v0.34.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.34.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.34.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v0.34.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.34.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
  • Deprecate deps.registerNodeLoader  -  by @​sheremet-va (7f45b)
    • This option was introduced to support aliasing inside external packages. Please, use deps.optimizer.web instead. If you test Node.js applications, consider adding external packages to server.deps.inline.
    View changes on GitHub

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

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 from f8e8639 to 37a35d7 Compare September 13, 2023 19:49
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from 2090d12 to b491796 Compare September 28, 2023 15:51
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 5 times, most recently from 450759d to 6ae002f Compare October 8, 2023 09:41
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 5 times, most recently from 392545b to 45b8aeb Compare October 17, 2023 15:45
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 45b8aeb to b1b501a Compare October 24, 2023 15:02
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b1b501a to c631d51 Compare October 31, 2023 16:27
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 75ad73b to 68f978e Compare November 9, 2023 16:40
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 5792c72 to a79f84c Compare November 16, 2023 17:09
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from a79f84c to 6dac7cb Compare January 24, 2024 16:38
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 6dac7cb to c0f1a65 Compare February 14, 2024 17:41
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from c0f1a65 to d5c84f3 Compare February 21, 2024 17:43
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d5c84f3 to 5508907 Compare March 13, 2024 16:28
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from 8217233 to d7cf8ff Compare April 10, 2024 15:57
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d7cf8ff to 80cd563 Compare April 10, 2024 16:07
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 66c1662 to 0a58b36 Compare May 1, 2024 14:50
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 0a58b36 to a2d1b08 Compare May 1, 2024 15:29
Copy link

sonarqubecloud bot commented May 1, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.34.0 chore(deps): update dependency vitest to ^0.34.0 - autoclosed May 1, 2024
@renovate renovate bot closed this May 1, 2024
@renovate renovate bot deleted the renovate/vitest-monorepo branch May 1, 2024 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

0 participants