-
-
Notifications
You must be signed in to change notification settings - Fork 23
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: update dependency vitest to v0.32.2 - autoclosed #688
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
6 times, most recently
from
February 28, 2023 09:15
ababdaa
to
94598db
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.28.5
chore: update dependency vitest to v0.29.0
Feb 28, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
February 28, 2023 13:56
94598db
to
bac9224
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.29.0
chore: update dependency vitest to v0.29.1
Feb 28, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 4, 2023 01:40
bac9224
to
331efb3
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.29.1
chore: update dependency vitest to v0.29.2
Mar 4, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 7, 2023 23:55
331efb3
to
7f1777b
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 18, 2023 20:22
7f1777b
to
6df9c3b
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.29.2
chore: update dependency vitest to v0.29.3
Mar 18, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
March 23, 2023 14:30
9ec4b64
to
73d6c53
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.29.3
chore: update dependency vitest to v0.29.5
Mar 23, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 23, 2023 20:42
73d6c53
to
144f2db
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.29.5
chore: update dependency vitest to v0.29.7
Mar 23, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 31, 2023 17:20
144f2db
to
eb4bd99
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.29.7
chore: update dependency vitest to v0.29.8
Mar 31, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
April 12, 2023 14:44
eb4bd99
to
14511cc
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.29.8
chore: update dependency vitest to v0.30.0
Apr 12, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
April 14, 2023 15:47
14511cc
to
7cd73fa
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.30.0
chore: update dependency vitest to v0.30.1
Apr 14, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
April 26, 2023 16:48
b408e81
to
b894c00
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
May 6, 2023 18:43
b894c00
to
06686fc
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.30.1
chore: update dependency vitest to v0.31.0
May 6, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
May 20, 2023 15:38
06686fc
to
18b4bd7
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.31.0
chore: update dependency vitest to v0.31.1
May 20, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
June 2, 2023 13:35
18b4bd7
to
e06a899
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.31.1
chore: update dependency vitest to v0.31.2
Jun 2, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
June 3, 2023 15:17
e06a899
to
f331ce1
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.31.2
chore: update dependency vitest to v0.31.3
Jun 3, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
June 4, 2023 13:19
f331ce1
to
aa1422d
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.31.3
chore: update dependency vitest to v0.31.4
Jun 4, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
6 times, most recently
from
June 9, 2023 18:57
7daca5f
to
d36c4e5
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.31.4
chore: update dependency vitest to v0.32.0
Jun 9, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
6 times, most recently
from
June 19, 2023 12:33
bccb293
to
02c1ab6
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.32.0
chore: update dependency vitest to v0.32.1
Jun 19, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
June 19, 2023 18:01
02c1ab6
to
824c34d
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.32.1
chore: update dependency vitest to v0.32.2
Jun 19, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
June 24, 2023 03:38
824c34d
to
ed2d9ff
Compare
renovate
bot
changed the title
chore: update dependency vitest to v0.32.2
chore: update dependency vitest to v0.32.2 - autoclosed
Jun 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.27.2
->0.32.2
Release Notes
vitest-dev/vitest
v0.32.2
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.32.1
Compare Source
🚀 Features
registerConsoleShortcuts
fromvitest/node
- by @deot in https://github.com/vitest-dev/vitest/issues/3563 (bc49b)expect.unreachable
- by @fenghan34 and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3556 (8e385)describe
/test
name support anonymous function - by @btea in https://github.com/vitest-dev/vitest/issues/3562 (3d436)🐞 Bug Fixes
performance
fromperf_hooks
- by @Max10240 and wangbaolong.wbl in https://github.com/vitest-dev/vitest/issues/3578 and https://github.com/vitest-dev/vitest/issues/3579 (24ec8)vitest
- by @userquin in https://github.com/vitest-dev/vitest/issues/3580 (b4ac8)View changes on GitHub
v0.32.0
Compare Source
🚨 Breaking Changes
test.js
to be a test file. Also any file in__tests__
is now considered to be a test, not just files withtest
orspec
suffix.@vitest/coverage-v8
package - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3339 (82112)@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 hasc8
as their coverage provider. Please, install the new@vitest/coverage-v8
package if you previously used@vitest/coverage-c8
.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
expect.soft
- by @Dunqing in https://github.com/vitest-dev/vitest/issues/3507 (7c687)describe
/test
name - by @fenghan34 in https://github.com/vitest-dev/vitest/issues/3497 (15253)🐞 Bug Fixes
View changes on GitHub
v0.31.4
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.31.3
Compare Source
🚀 Features
VITE_NODE_DEPS_MODULE_DIRECTORIES
from .npmrc - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3471 (393bf)🐞 Bug Fixes
View changes on GitHub
v0.31.2
Compare Source
🚀 Features
test.each
ordescribe.each
- by @fenghan34 and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3360 (7c2f7)reportOnFailure
option - by @AriPerkkio and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3453 (1988f)🐞 Bug Fixes
SIGINT
is received - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3407 (a2cc2)rejects
&resolves
breaks with thenable objects - by @fenghan34 in https://github.com/vitest-dev/vitest/issues/3456 (4e996)birpc
timeouts whenMath.random
mock is not restored - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3460 (cd5d5)less
extension - by @rluvaton in https://github.com/vitest-dev/vitest/issues/3465 (4d045)PartialMock
with async TReturns - by @ghry5 in https://github.com/vitest-dev/vitest/issues/3462 (b664d)View changes on GitHub
v0.31.1
Compare Source
🚀 Features
r
should rerun current pattern tests - by @Dunqing and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3305 (69d27)🐞 Bug Fixes
cwd
from test name filter - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3353 (324a9)toMatchInlineSnapshot
fails when file path includes parentheses - by @pacexy in https://github.com/vitest-dev/vitest/issues/3370 and https://github.com/vitest-dev/vitest/issues/3371 (dcf13)View changes on GitHub
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
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.
This PR has been generated by Mend Renovate. View repository job log here.