-
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
Update vitest monorepo to v1.6.0 #196
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.
Open
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
May 10, 2024 11:45
6ebab9f
to
d9fa775
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
May 14, 2024 14:30
d9fa775
to
5e77ebd
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
4 times, most recently
from
June 4, 2024 10:55
8f28c0c
to
77cb696
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
3 times, most recently
from
June 11, 2024 10:42
51c392c
to
7cf9bdc
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
4 times, most recently
from
June 24, 2024 16:45
6249048
to
c7464dd
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
4 times, most recently
from
July 9, 2024 09:23
4bf1502
to
eca7a25
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
July 17, 2024 09:36
6e4696e
to
eef7938
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
July 24, 2024 11:06
91e947d
to
cf4a674
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
4 times, most recently
from
September 30, 2024 09:18
fcfa4f7
to
bebbad0
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
3 times, most recently
from
October 9, 2024 12:25
d26e6c7
to
56abe7a
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
6 times, most recently
from
October 24, 2024 10:04
457bb29
to
194efec
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
4 times, most recently
from
November 4, 2024 10:57
fc578d9
to
0d61cd9
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
November 6, 2024 09:32
0d61cd9
to
47583bd
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
6 times, most recently
from
November 28, 2024 11:14
b5a6f98
to
ac1edcf
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
December 4, 2024 15:25
ba07c87
to
7ca6c77
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
2 times, most recently
from
January 3, 2025 10:59
3717c0e
to
c8cfbdf
Compare
renovate
bot
force-pushed
the
renovate/vitest-monorepo
branch
from
January 3, 2025 14:21
c8cfbdf
to
82db041
Compare
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:
1.5.3
->1.6.0
1.5.3
->1.6.0
Release Notes
vitest-dev/vitest (@vitest/coverage-v8)
v1.6.0
Compare Source
🚀 Features
includeConsoleOutput
andaddFileAttribute
in junit - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5659 (2f913)🐞 Bug Fixes
resolveId('vitest')
afterbuildStart
- by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5646 (f5faf)toJSON
for error serialization - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5526 (19a21)*.test-d.*
by default - by @MindfulPol in https://github.com/vitest-dev/vitest/issues/5634 (bfe8a)vite-node
's wrapper only to executed files - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5642 (c9883)🏎 Performance
View changes on GitHub
Configuration
📅 Schedule: Branch creation - "after 7am and before 11am every weekday" in timezone Europe/London, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.