Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update dependency vitest to v2 #685

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dependency vitest to v2 #685

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 5, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) 0.34.6 -> 2.1.8 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

v2.1.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.7

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.6

Compare Source

🚀 Features

  • Support VIte 6
    View changes on GitHub

v2.1.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.3

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.0

Compare Source

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

  await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()

  const [firstPost] = screen.getByRole('listitem').all()

  await firstPost.getByRole('button', { name: 'Delete' }).click()

  expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.0.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.0.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.3

Compare Source

   🚀 Features
   🐞 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 this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate Renovate
Copy link
Contributor Author

renovate bot commented Dec 5, 2023 •
edited
Loading

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @vitest/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/vitest
npm ERR!   dev vitest@"1.6.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vitest@">=0.30.0 <1" from @vitest/[email protected]
npm ERR! node_modules/@vitest/coverage-c8
npm ERR!   dev @vitest/coverage-c8@"0.33.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/vitest
npm ERR!   peer vitest@">=0.30.0 <1" from @vitest/[email protected]
npm ERR!   node_modules/@vitest/coverage-c8
npm ERR!     dev @vitest/coverage-c8@"0.33.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-03T15_42_56_361Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 4 times, most recently from ff27011 to a9993d3 Compare December 9, 2023 22:05
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from a9993d3 to 039d30f Compare December 19, 2023 16:47
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from cb13a00 to 2b35ee5 Compare January 5, 2024 09:59
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 7e7e119 to 2d9883c Compare January 17, 2024 17:00
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 2d9883c to 06535e5 Compare January 26, 2024 17:40
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 08a5df0 to 3a9b053 Compare February 20, 2024 16:32
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 3a9b053 to bb00acf Compare March 15, 2024 10:58
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from bb00acf to 2ae2687 Compare April 11, 2024 19:02
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 2109293 to f636f53 Compare April 30, 2024 11:04
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from f636f53 to 1218a99 Compare May 3, 2024 15:43
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 1218a99 to 97d7aee Compare July 9, 2024 11:55
@renovate renovate bot changed the title Update dependency vitest to v1 Update dependency vitest to v2 Jul 9, 2024
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jul 9, 2024 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @vitest/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/vitest
npm ERR!   dev vitest@"2.1.8" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vitest@">=0.30.0 <1" from @vitest/[email protected]
npm ERR! node_modules/@vitest/coverage-c8
npm ERR!   dev @vitest/coverage-c8@"0.33.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/vitest
npm ERR!   peer vitest@">=0.30.0 <1" from @vitest/[email protected]
npm ERR!   node_modules/@vitest/coverage-c8
npm ERR!     dev @vitest/coverage-c8@"0.33.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-12-11T22_00_55_010Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 325882f to 559c6a4 Compare July 15, 2024 11:00
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 559c6a4 to f99b9f3 Compare July 22, 2024 10:41
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from f99b9f3 to da3a4af Compare July 31, 2024 12:38
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 2ec0de4 to 38d6116 Compare September 13, 2024 18:42
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 38d6116 to 1d465cf Compare October 2, 2024 19:41
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 1d465cf to c8faae5 Compare October 14, 2024 19:58
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 952a7f7 to e3ba70c Compare October 30, 2024 00:21
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from e3ba70c to fc10a63 Compare November 13, 2024 17:04
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 47d40bb to 2b354f7 Compare December 2, 2024 17:09
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 2b354f7 to 4884f4c Compare December 11, 2024 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants