-
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 vitest monorepo to v0.34.6 #45
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/vitest-monorepo
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
changed the title
chore(deps): update vitest monorepo to v0.29.3
chore(deps): update vitest monorepo to v0.29.5
Mar 20, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
March 20, 2023 21:52
7d6a4cc
to
d6760ec
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.29.5
chore(deps): update vitest monorepo to v0.29.7
Mar 20, 2023
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.29.7
chore(deps): update vitest monorepo to v0.29.8
Mar 28, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 28, 2023 20:16
d6760ec
to
e608488
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
April 9, 2023 15:18
e608488
to
d56ed92
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.29.8
chore(deps): update vitest monorepo to v0.30.0
Apr 9, 2023
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
from
April 11, 2023 14:35
d56ed92
to
5ba3d11
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
from
May 3, 2023 21:29
5ba3d11
to
9ffae70
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.31.0
chore(deps): update vitest monorepo to v0.31.4
Jun 1, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
June 6, 2023 20:47
07b93c4
to
414764e
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.31.4
chore(deps): update vitest monorepo to v0.32.0
Jun 6, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
June 16, 2023 15:09
414764e
to
304cbde
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.32.0
chore(deps): update vitest monorepo to v0.32.1
Jun 16, 2023
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.32.1
chore(deps): update vitest monorepo to v0.32.2
Jun 16, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
June 16, 2023 20:14
304cbde
to
3b3e3e7
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.32.2
chore(deps): update vitest monorepo to v0.32.3
Jul 3, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
July 3, 2023 13:53
fb239fd
to
852dc51
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.32.3
chore(deps): update vitest monorepo to v0.32.4
Jul 3, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
July 6, 2023 17:25
852dc51
to
902320a
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.32.4
chore(deps): update vitest monorepo to v0.33.0
Jul 6, 2023
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.33.0
chore(deps): update vitest monorepo to v0.34.0
Aug 1, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 1, 2023 16:18
902320a
to
cf17fc7
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.34.0
chore(deps): update vitest monorepo to v0.34.1
Aug 1, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 1, 2023 18:45
cf17fc7
to
3d6ad1f
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 17, 2023 11:08
3d6ad1f
to
7de0f71
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.34.1
chore(deps): update vitest monorepo to v0.34.2
Aug 17, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
August 25, 2023 07:54
7de0f71
to
c7325f7
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.34.2
chore(deps): update vitest monorepo to v0.34.3
Aug 25, 2023
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.34.3
chore(deps): update vitest monorepo to v0.34.4
Sep 8, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
September 8, 2023 13:01
c7325f7
to
8185b8b
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
September 21, 2023 15:30
8185b8b
to
5d5e65a
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.34.4
chore(deps): update vitest monorepo to v0.34.5
Sep 21, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
September 29, 2023 16:36
5d5e65a
to
7882747
Compare
renovate
bot
changed the title
chore(deps): update vitest monorepo to v0.34.5
chore(deps): update vitest monorepo to v0.34.6
Sep 29, 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.29.2
->0.34.6
0.29.2
->0.34.6
Release Notes
vitest-dev/vitest (@vitest/coverage-istanbul)
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
v0.33.0
Compare Source
🚨 Breaking Changes
0.32.0
changed the defaultinclude
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
concurrent
option tosequence
config - by @fenghan34 and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3604 (f427f)bench
name - by @fenghan34 in https://github.com/vitest-dev/vitest/issues/3711 (a749a)test.extend
- by @fenghan34 in https://github.com/vitest-dev/vitest/issues/3554 (2db1a)🐞 Bug Fixes
CTRL+C
to terminate run - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3642 (fa663)toBeCalledTimes
- by @antfu in https://github.com/vitest-dev/vitest/issues/3696 (d3640)v8
to prevent crash on dynamic CJS files - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3657 (40f18)retry
andrepeats
0 - by @Dunqing in https://github.com/vitest-dev/vitest/issues/3638 (6d146)h
key - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3618 (60c36)View changes on GitHub
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
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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.