Skip to content
This repository was archived by the owner on Mar 20, 2025. It is now read-only.

chore(deps): update vitest monorepo to v2 (major) - autoclosed #555

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 25, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-v8 (source) ^0.34.0 -> ^2.0.0 age adoption passing confidence
vitest (source) ^0.34.0 -> ^2.0.0 age adoption passing confidence

Release Notes

vitest-dev/vitest (@​vitest/coverage-v8)

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

   🐞 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 - "* 0-3 * * 1" (UTC), 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.


  • 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 bot requested a review from a team as a code owner December 25, 2023 01:26
@renovate renovate bot added dependencies Pull requests that update a dependency file javascript labels Dec 25, 2023
Copy link
Contributor Author

renovate bot commented Dec 25, 2023

⚠ 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: [email protected]
npm ERR! Found: @types/[email protected]
npm ERR! node_modules/@types/node
npm ERR!   dev @types/node@"^14.18.32" from the root project
npm ERR!   peer @types/node@"*" from [email protected]
npm ERR!   node_modules/cosmiconfig-typescript-loader
npm ERR!     cosmiconfig-typescript-loader@"^4.0.0" from @commitlint/[email protected]
npm ERR!     node_modules/@commitlint/load
npm ERR!       @commitlint/load@"^17.8.1" from @commitlint/[email protected]
npm ERR!       node_modules/@commitlint/cli
npm ERR!         dev @commitlint/cli@"^17.0.0" from the root project
npm ERR!         1 more (@netlify/eslint-config-node)
npm ERR!   2 more (ts-node, vite)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @types/node@"^18.0.0 || >=20.0.0" from [email protected]
npm ERR! node_modules/vitest
npm ERR!   dev vitest@"^1.0.0" from the root project
npm ERR!   peer vitest@"^1.0.0" from @vitest/[email protected]
npm ERR!   node_modules/@vitest/coverage-v8
npm ERR!     dev @vitest/coverage-v8@"^1.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @types/[email protected]
npm ERR! node_modules/@types/node
npm ERR!   peerOptional @types/node@"^18.0.0 || >=20.0.0" from [email protected]
npm ERR!   node_modules/vitest
npm ERR!     dev vitest@"^1.0.0" from the root project
npm ERR!     peer vitest@"^1.0.0" from @vitest/[email protected]
npm ERR!     node_modules/@vitest/coverage-v8
npm ERR!       dev @vitest/coverage-v8@"^1.0.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/2023-12-25T01_26_41_119Z-debug-0.log

kodiakhq[bot]
kodiakhq bot previously approved these changes Dec 25, 2023
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from ae98b30 to 698d6bf Compare July 8, 2024 13:32
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v1 (major) chore(deps): update vitest monorepo to v2 (major) Jul 8, 2024
Copy link
Contributor Author

renovate bot commented Jul 8, 2024

⚠️ 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: [email protected]
npm ERR! Found: @types/[email protected]
npm ERR! node_modules/@types/node
npm ERR!   dev @types/node@"^14.18.32" from the root project
npm ERR!   peer @types/node@"*" from [email protected]
npm ERR!   node_modules/cosmiconfig-typescript-loader
npm ERR!     cosmiconfig-typescript-loader@"^4.0.0" from @commitlint/[email protected]
npm ERR!     node_modules/@commitlint/load
npm ERR!       @commitlint/load@"^17.8.1" from @commitlint/[email protected]
npm ERR!       node_modules/@commitlint/cli
npm ERR!         dev @commitlint/cli@"^17.0.0" from the root project
npm ERR!         1 more (@netlify/eslint-config-node)
npm ERR!   2 more (ts-node, vite)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @types/node@"^18.0.0 || >=20.0.0" from [email protected]
npm ERR! node_modules/vitest
npm ERR!   dev vitest@"^2.0.0" from the root project
npm ERR!   peer vitest@"2.0.0" from @vitest/[email protected]
npm ERR!   node_modules/@vitest/coverage-v8
npm ERR!     dev @vitest/coverage-v8@"^2.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @types/[email protected]
npm ERR! node_modules/@types/node
npm ERR!   peerOptional @types/node@"^18.0.0 || >=20.0.0" from [email protected]
npm ERR!   node_modules/vitest
npm ERR!     dev vitest@"^2.0.0" from the root project
npm ERR!     peer vitest@"2.0.0" from @vitest/[email protected]
npm ERR!     node_modules/@vitest/coverage-v8
npm ERR!       dev @vitest/coverage-v8@"^2.0.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-07-08T13_31_51_040Z-debug-0.log

@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2 (major) chore(deps): update vitest monorepo to v2 (major) - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/major-vitest-monorepo branch December 8, 2024 18:54
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file javascript
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants