-
-
Notifications
You must be signed in to change notification settings - Fork 1
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 v0.31.0 - autoclosed #204
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
3 times, most recently
from
October 31, 2022 11:42
bba9953
to
4206e77
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.24.3
chore(deps): update vitest monorepo to v0.24.4
Oct 31, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
4 times, most recently
from
November 1, 2022 19:01
5255b36
to
e90aa03
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.24.4
chore(deps): update vitest monorepo to v0.24.5
Nov 1, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
3 times, most recently
from
November 7, 2022 16:44
6ea2339
to
4061df2
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.24.5
chore(deps): update vitest monorepo to v0.25.0
Nov 7, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
November 8, 2022 16:10
7b544a3
to
835d108
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.25.0
chore(deps): update vitest monorepo to v0.25.1
Nov 8, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
November 14, 2022 14:45
835d108
to
15f6806
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.25.1
chore(deps): update vitest monorepo to v0.25.2
Nov 14, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
4 times, most recently
from
November 16, 2022 01:13
bd48b48
to
8f03346
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
November 22, 2022 13:13
e170d2c
to
259edbf
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.25.2
chore(deps): update vitest monorepo to v0.25.3
Nov 22, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
November 28, 2022 21:48
8a7e483
to
8ae9500
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
December 5, 2022 14:07
21aa4fb
to
db55d10
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.30.0
chore(deps): update vitest monorepo to v0.30.1
Apr 11, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
8 times, most recently
from
April 23, 2023 13:16
bdd6612
to
e5f0c45
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
7 times, most recently
from
May 2, 2023 00:17
f5accda
to
b34bae5
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
May 3, 2023 19:55
c9222b0
to
498dbb0
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.30.1
chore(deps): update vitest monorepo to v0.31.0
May 3, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
5 times, most recently
from
May 9, 2023 04:11
70d348a
to
f54ad78
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
May 10, 2023 13:45
f54ad78
to
4b54902
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.31.0
chore(deps): update dependency vitest to v0.31.0
May 10, 2023
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.31.0
chore(deps): update dependency vitest to v0.31.0 - autoclosed
May 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.23.4
->0.31.0
Release Notes
vitest-dev/vitest
v0.31.0
Compare Source
🚨 Breaking Changes
Remove
browser
from allowed pools insidepoolMatchGlob
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)
🚀 Features
vi.hoisted
to run code before imports are executed:vi.mock
:--bail
option for cancelling test run - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3163 (8d460)🐞 Bug Fixes
thresholdAutoUpdate
to work withperFile
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3182 (29eeb)import.meta.hot.send
mock - by @antfu (b1624)View changes on GitHub
v0.30.1
Compare Source
🐞 Bug Fixes
performance
andAggregateError
- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3171 (cce45)test.each
respectschaiConfig
- by @sheremet-va (4f6c1)toMatchFileSnapshot
ensure dir exists - by @antfu in https://github.com/vitest-dev/vitest/issues/3155 (31168)skipWriting
check - by @antfu (5436c)toMatchFileSnapshot
- by @antfu in https://github.com/vitest-dev/vitest/issues/3164 (df3f2)View changes on GitHub
v0.30.0
Compare Source
🚨 Breaking Changes
🚀 Features
toMatchFileSnapshot
and auto queuing expect promise - by @antfu in https://github.com/vitest-dev/vitest/issues/3116 (bdc06)🐞 Bug Fixes
View changes on GitHub
v0.29.8
Compare Source
🚀 Features
istanbul
coverage support for browser testing - by @sheremet-va and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3040 (0f44d)🐞 Bug Fixes
View changes on GitHub
v0.29.7
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.6
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.5
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.4
Compare Source
🚀 Features
--test-timeout
CLI argument - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3019 (63c62)🐞 Bug Fixes
View changes on GitHub
v0.29.3
Compare Source
🚀 Features
🐞 Bug Fixes
any
as default value for TArgs in vi.fn() - by @jessevanassen in https://github.com/vitest-dev/vitest/issues/2947 (1bdcc)🏎 Performance
View changes on GitHub
v0.29.2
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.0
Compare Source
This release makes some significant changes to how tests are running. If you were using
--no-threads
before, you might consider enabling--single-thread
instead (because your tests are now running inchild_process
instead of a worker thread) or try our new performance optimization feature (discussed later). If you were relying on API that was not available inside a worker (likeprocess.chdir()
, you can now use this option.One of the potential breaking bug fixes is that environments do not share the same global scope anymore if you run them with
--no-isolate
,--no-threads
or--single-thread
- you might need to update your setup files if you were relying on a global variable before.If you had performance issues on large code bases before, try the new
deps.experimentalOptimizer
option instead of disabling threads. Feedback is welcome!One of the breaking changes includes adding a link to snapshots inside snapshot files, meaning you will need to update all your snapshots.
🚨 Breaking Changes
NODE_V8_COVERAGE
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2786 (095c6)node
andjsdom
(and other environments) now don't share the same global scope, if you run them with--no-isolate
or--no-threads
flag. Vitest doesn't provide a way to restore the previous behavior as it is considered a bug.chid_process
might run longer due to the communication overhead. If you want to restore the previous behavior, use--single-thread
.🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.28.5
Compare Source
🚀 Features
🐞 Bug Fixes
🏎 Performance
View changes on GitHub
v0.28.4
Compare Source
🐞 Bug Fixes
onWatcherStart
whentypecheck.ignoreSourceErrors
is true - by @mascii and @sheremet-va in https://github.com/vitest-dev/vitest/issues/2774 (d612e)View changes on GitHub
v0.28.3
Compare Source
🚀 Features
config
option to be false - by @antfu in https://github.com/vitest-dev/vitest/issues/2749 (c66e3)🐞 Bug Fixes
🏎 Performance
View changes on GitHub
v0.28.2
Compare Source
🐞 Bug Fixes
timestamp: 0
- by @danielroe in https://github.com/vitest-dev/vitest/issues/2747 (e88c0)View changes on GitHub
v0.28.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.28.0
Compare Source
🚨 Breaking Changes
@vitet/runner
package instead ofvitest
🐞 Bug Fixes
View changes on GitHub
v0.27.3
Compare Source
🚀 Features
environmentMatchGlobs
option to auto infer env based on glob - by @antfu in https://github.com/vitest-dev/vitest/issues/2714 (3e142)🐞 Bug Fixes
reportCoverage
context can be optional - by @antfu (4cd1e)View changes on GitHub
v0.27.2
Compare Source
🚀 Features
🐞 Bug Fixes
coverage.all
only when all tests are run - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2665 (85096)🏎 Performance
View changes on GitHub
v0.27.1
Compare Source
🚀 Features
🐞 Bug Fixes
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.
This PR has been generated by Mend Renovate. View repository job log here.