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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 6, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-c8 (source) ^0.31.4 -> ^0.33.0 age adoption passing confidence
@vitest/ui (source) ^0.31.4 -> ^0.34.7 age adoption passing confidence
vitest (source) ^0.31.4 -> ^0.34.6 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
vitest-dev/vitest (@​vitest/ui)

v0.34.7

Compare Source

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

Configuration

📅 Schedule: Branch creation - "after 11pm on sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.

@changeset-bot
Copy link

changeset-bot bot commented Jun 6, 2023

⚠️ No Changeset found

Latest commit: a3878df

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 9 times, most recently from acbed22 to aee3c67 Compare June 13, 2023 09:08
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from aee3c67 to da04d36 Compare June 15, 2023 20:19
@renovate renovate bot changed the title chore(deps): update vitest monorepo to ^0.32.0 chore(deps): update vitest monorepo to ^0.32.1 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from da04d36 to 085e240 Compare June 16, 2023 14:11
@renovate renovate bot changed the title chore(deps): update vitest monorepo to ^0.32.1 chore(deps): update vitest monorepo to ^0.32.2 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 8 times, most recently from 8a1842f to eac68c7 Compare June 23, 2023 00:16
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 8 times, most recently from d05a8ba to 25faf91 Compare June 24, 2023 23:14
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 8 times, most recently from 81a5bcd to 560ccad Compare November 20, 2023 01:10
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 8ee4368 to 1ffb056 Compare November 27, 2023 03:19
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 6 times, most recently from 39b1120 to f822ff3 Compare December 4, 2023 17:35
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 7 times, most recently from dee786d to f9451da Compare December 12, 2023 21:17
@renovate renovate bot changed the title chore(deps): update vitest monorepo chore(deps): update vitest monorepo - autoclosed Dec 14, 2023
@renovate renovate bot closed this Dec 14, 2023
@renovate renovate bot deleted the renovate/vitest-monorepo branch December 14, 2023 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants