-
Notifications
You must be signed in to change notification settings - Fork 0
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.30.1 - autoclosed #21
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
Branch automerge failureThis PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
|
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
November 14, 2022 14:49
f56c652
to
f1ecc86
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.25.1
chore(deps): update dependency vitest to v0.25.2
Nov 14, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
3 times, most recently
from
November 22, 2022 15:54
e23bd26
to
0344cc5
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.25.2
chore(deps): update dependency vitest to v0.25.3
Nov 22, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
3 times, most recently
from
December 5, 2022 07:04
3061363
to
1b5d786
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
December 5, 2022 20:16
9e3df14
to
e3bf69b
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.25.3
chore(deps): update dependency vitest to v0.25.4
Dec 6, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 6, 2022 18:53
e3bf69b
to
b3f836d
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.25.4
chore(deps): update dependency vitest to v0.25.5
Dec 6, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 8, 2022 13:28
b3f836d
to
eda945f
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.25.5
chore(deps): update dependency vitest to v0.25.6
Dec 8, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 10, 2022 21:11
eda945f
to
64b2e56
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.25.6
chore(deps): update dependency vitest to v0.25.7
Dec 11, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
4 times, most recently
from
December 13, 2022 11:05
f6ddccb
to
2068746
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.25.7
chore(deps): update dependency vitest to v0.25.8
Dec 13, 2022
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
3 times, most recently
from
December 19, 2022 11:30
bf1798b
to
a485750
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
3 times, most recently
from
March 13, 2023 04:03
af4aab0
to
087402e
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 13, 2023 08:03
087402e
to
7b4751d
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.29.2
chore(deps): update dependency vitest to v0.29.3
Mar 15, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
4 times, most recently
from
March 20, 2023 16:36
c27711d
to
8fa50b9
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.29.3
chore(deps): update dependency vitest to v0.29.5
Mar 20, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 20, 2023 21:37
8fa50b9
to
05bbe0f
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.29.5
chore(deps): update dependency vitest to v0.29.7
Mar 20, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
5 times, most recently
from
March 28, 2023 18:27
2a48f0b
to
0e23cde
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.29.7
chore(deps): update dependency vitest to v0.29.8
Mar 28, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
3 times, most recently
from
April 9, 2023 15:38
9eb2933
to
67122b3
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.29.8
chore(deps): update dependency vitest to v0.30.0
Apr 9, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
April 11, 2023 15:37
67122b3
to
4bac1d6
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.30.0
chore(deps): update dependency vitest to v0.30.1
Apr 11, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
April 14, 2023 13:36
4bac1d6
to
4657478
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
April 14, 2023 17:30
4657478
to
837f655
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.30.1
chore(deps): update dependency vitest to v0.30.1 - autoclosed
Apr 14, 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.12.2
->0.30.1
Release Notes
vitest-dev/vitest
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
coverage.extension
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2641 (7e388)View changes on GitHub
v0.27.0
Compare Source
🚨 Breaking Changes
🚀 Features
🐞 Bug Fixes
🏎 Performance
View changes on GitHub
v0.26.3
Compare Source
🚀 Features
importOriginal
helper to the factory - by @antfu in https://github.com/vitest-dev/vitest/issues/2551 (853ee)🐞 Bug Fixes
View changes on GitHub
v0.26.2
Compare Source
🚀 Features
🐞 Bug Fixes
dir
- by @antfu in https://github.com/vitest-dev/vitest/issues/2550 (f6b59)View changes on GitHub
v0.26.1
Compare Source
🚀 Features
🐞 Bug Fixes
[View changes on GitHub](https://github.com/vitest-dev/vitest/compare/v0.26.0...v0.26
Configuration
📅 Schedule: Branch creation - "before 7am on Monday" in timezone Canada/Eastern, 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.