-
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 ^0.34.0 #144
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 dependency vitest to v1.0.2
chore(deps): update dependency vitest to v1.0.3
Dec 9, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
December 9, 2023 19:46
730c83a
to
2acfd7a
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v1.0.3
chore(deps): update dependency vitest to v1.0.4
Dec 9, 2023
renovate
bot
changed the title
chore(deps): update dependency vitest to v1.0.4
chore(deps): update dependency vitest to v1.1.0
Dec 19, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
December 19, 2023 15:18
2acfd7a
to
69255a3
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v1.1.0
chore(deps): update dependency vitest to v1.1.1
Dec 31, 2023
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
January 4, 2024 20:18
ee759e4
to
5b9c1be
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v1.1.1
chore(deps): update dependency vitest to v1.1.2
Jan 4, 2024
renovate
bot
changed the title
chore(deps): update dependency vitest to v1.1.2
chore(deps): update dependency vitest to v1.1.3
Jan 5, 2024
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
January 5, 2024 10:41
5b9c1be
to
20b8551
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v1.1.3
chore(deps): update dependency vitest to v1.1.3 - autoclosed
Jan 8, 2024
renovate
bot
changed the title
chore(deps): update dependency vitest to v1.1.3 - autoclosed
chore(deps): update dependency vitest to v1.1.3
Jan 12, 2024
renovate
bot
changed the title
chore(deps): update dependency vitest to v1.1.3
chore(deps): update dependency vitest to v1.2.0
Jan 12, 2024
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
January 12, 2024 20:10
20b8551
to
695283d
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v1.2.0
chore(deps): update dependency vitest to v1.2.1
Jan 17, 2024
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
January 17, 2024 18:59
695283d
to
2e34efa
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
January 26, 2024 19:46
2e34efa
to
1f29b1a
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v1.2.1
chore(deps): update dependency vitest to v1.2.2
Jan 26, 2024
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
February 16, 2024 18:46
1f29b1a
to
dcf9dca
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v1.2.2
chore(deps): update dependency vitest to v1.3.0
Feb 16, 2024
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
February 20, 2024 14:08
dcf9dca
to
85aaf47
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v1.3.0
chore(deps): update dependency vitest to v1.3.1
Feb 20, 2024
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 5, 2024 10:02
85aaf47
to
e7225b7
Compare
renovate
bot
changed the title
chore(deps): update dependency vitest to v1.3.1
chore(deps): update dependency vitest to ^0.34.0
Mar 5, 2024
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
March 12, 2024 13:20
e7225b7
to
b44cc4e
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
April 24, 2024 13:13
b44cc4e
to
666ae6a
Compare
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.32.4
->^0.34.0
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
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
Configuration
📅 Schedule: Branch creation - "* 0-4,22-23 * * 1-5,* * * * 0,6" in timezone Europe/Brussels, 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 was generated by Mend Renovate. View the repository job log.