-
-
Notifications
You must be signed in to change notification settings - Fork 720
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.34.6 - autoclosed #4515
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 16, 2023 12:53
1960782
to
283f29c
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 16, 2023 13:40
283f29c
to
5096ace
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 16, 2023 13:57
5096ace
to
f654ea9
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 17, 2023 07:44
f654ea9
to
22e75a5
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 17, 2023 13:05
22e75a5
to
6a1e510
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 17, 2023 14:56
6a1e510
to
0fb9e47
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 17, 2023 15:34
0fb9e47
to
b6dfdcd
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 17, 2023 18:42
b6dfdcd
to
0ac9e86
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 17, 2023 21:55
0ac9e86
to
c0ff246
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 18, 2023 08:41
c0ff246
to
2e92471
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 18, 2023 11:27
2e92471
to
fd5d8da
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 18, 2023 11:56
fd5d8da
to
125a397
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 21, 2023 07:00
125a397
to
d98b224
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 19, 2023 14:02
90b29d7
to
6c64189
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 19, 2023 14:37
6c64189
to
81d429b
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
December 19, 2023 19:05
d5393cd
to
da1104b
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 19, 2023 19:17
da1104b
to
f120d7c
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 20, 2023 07:16
f120d7c
to
f4d9640
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 20, 2023 08:18
f4d9640
to
0d86b45
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 20, 2023 09:11
0d86b45
to
3a256df
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 20, 2023 09:48
3a256df
to
2b4b1e3
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 20, 2023 10:46
2b4b1e3
to
0de2a8e
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 20, 2023 11:49
0de2a8e
to
d879920
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 20, 2023 13:01
d879920
to
e6abe6a
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 20, 2023 13:21
e6abe6a
to
3cddc3f
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v0.34.6
chore(deps): update dependency vitest to v0.34.6 - autoclosed
Dec 20, 2023
auto-merge was automatically disabled
December 20, 2023 13:49
Pull request was closed
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.33.0
->0.34.6
Release Notes
vitest-dev/vitest (vitest)
v0.34.6
Compare Source
🐞 Bug Fixes
test.extend
should be init once time in all test - by @Dunqing in https://github.com/vitest-dev/vitest/issues/4168 (730b2)View changes on GitHub
v0.34.5
Compare Source
🚀 Features
diff
option - by @fenghan34 and @sheremet-va in https://github.com/vitest-dev/vitest/issues/4063 (b50cf)coverage['100']
to istanbul provider - by @marcelobotega in https://github.com/vitest-dev/vitest/issues/4109 (a7e09)vi.waitFor
method - by @Dunqing and @sheremet-va in https://github.com/vitest-dev/vitest/issues/4113 (d79cb)vi.waitUntil
method - by @Dunqing and @sheremet-va in https://github.com/vitest-dev/vitest/issues/4129 (e0ac9)🐞 Bug Fixes
toThrow
- by @Dunqing in https://github.com/vitest-dev/vitest/issues/3979 (725a0)testNamePattern
- by @segrey in https://github.com/vitest-dev/vitest/issues/4103 and https://github.com/vitest-dev/vitest/issues/4104 (3c305)test.extend
doesn't work in hooks without test - by @Dunqing in https://github.com/vitest-dev/vitest/issues/4065 (175c7)SourceMapInput
to fix CYCLIC_CROSS_CHUNK_REEXPORT - by @Dunqing in https://github.com/vitest-dev/vitest/issues/4128 (ca70a)🏎 Performance
View changes on GitHub
v0.34.4
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.34.3
Compare Source
🚀 Features
allowExternal
option - by @vojvodics and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3894 (c03fa)vitest/reporters
- by @Dunqing and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3980 (5704b)🐞 Bug Fixes
View changes on GitHub
v0.34.2
Compare Source
🚀 Features
--experimental-vm-threads
- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3880 (f4e6e)ctx.skip()
inside the running test - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3966 (5c88d)🐞 Bug Fixes
execute.d.ts
- by @btea in https://github.com/vitest-dev/vitest/issues/3970 (0f8e6)?inline
query is specified - by @thebanjomatic and Adam Hines in https://github.com/vitest-dev/vitest/issues/3952 (3891d)🏎 Performance
View changes on GitHub
v0.34.1
Compare Source
🐞 Bug Fixes
--experimental-vm-worker-memory-limit
totinypool
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3856 (3c67a)View changes on GitHub
v0.34.0
Compare Source
🚨 Breaking Changes
transformMode
is now moved toserver.transformMode
. This option is highly discouraged to use. If you need to change the transform mode, use the new optiontestTransformMode
instead to control the mode based on the running test, not the current file path. By default, tests withjsdom
orhappy-dom
useweb
transform mode, and tests usingnode
oredge
environment usessr
mode. If you have a custom environment, it should providetransformMode
property.coverage.reportOnFailure
by default - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3615 (0c6f6)@vitest/coverage-c8
package - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3614 (a90d6)@vitest/coverage-c8
is no longer supported. Please, use@vitest/coverage-v8
instead.experimentalVmThreads
pool to run your tests using VM Sandboxes environment. Make sure you understand all pitfalls of this pool before opening an issue.server
option - by @fenghan34 and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3725 (dc4fa)deps.
options are now moved toserver.deps
with a deprecation warning. Please, consider usingdeps.optimizer
instead ofdeps.inline
/deps.external
. Ideally, we would like to move away from usingserver.deps.inline
altogether.vite-node index.ts --watch
, you now have to dovite-node --watch index.ts
.deps.optimizer
is now enabled by default. This means that Vitest will bundle specified dependencies before running your tests. This field inherits options fromoptimizeDeps
andssr.optimizeDeps
which are populated by other plugins (like, Svelte).🚀 Features
describe.sequential
- by @fenghan34 and @dammy001 in https://github.com/vitest-dev/vitest/issues/3771 (86934)--related --watch
reruns non-affected tests if they were changed during a run - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3844 (c9aea)🐞 Bug Fixes
defineConfig
type from vite - by @sodatea in https://github.com/vitest-dev/vitest/issues/3804 (9c8e3)toStrictEqual
- by @Dunqing (52aef)istanbul-lib-instrument
to v6 to fix vulnerable dependency - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3814 (f3bd9)🏎 Performance
deps.optimizer.web
instead. If you test Node.js applications, consider adding external packages toserver.deps.inline
.View changes on GitHub
Configuration
📅 Schedule: Branch creation - "after 7pm every weekday,before 5am every weekday" in timezone Europe/Madrid, 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.