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.

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 dependency vitest to v2 - autoclosed #4

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 23, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) ^1.5.0 -> ^2.1.4 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

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
    View changes on GitHub

v2.0.2

Compare Source

v2.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.0

Compare Source

Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.

🚨 Breaking Changes

Configuration

📅 Schedule: Branch creation - "after 9am and before 1pm on Saturday" in timezone Asia/Tokyo, 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.

Copy link
Contributor Author

renovate bot commented Aug 23, 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @cloudflare/vitest-pool-workers@0.4.29
npm error Found: vitest@2.1.4
npm error node_modules/vitest
npm error   dev vitest@"^2.1.4" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vitest@"1.3.x - 1.5.x" from @cloudflare/vitest-pool-workers@0.4.29
npm error node_modules/@cloudflare/vitest-pool-workers
npm error   dev @cloudflare/vitest-pool-workers@"^0.4.29" from the root project
npm error
npm error Conflicting peer dependency: vitest@1.5.3
npm error node_modules/vitest
npm error   peer vitest@"1.3.x - 1.5.x" from @cloudflare/vitest-pool-workers@0.4.29
npm error   node_modules/@cloudflare/vitest-pool-workers
npm error     dev @cloudflare/vitest-pool-workers@"^0.4.29" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-10-28T14_44_34_671Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-10-28T14_44_34_671Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 7e59721 to 451d34b Compare August 31, 2024 04:12
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 451d34b to cf6385c Compare August 31, 2024 04:17
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 0ce85ae to 8f96d1c Compare September 13, 2024 15:43
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 8f96d1c to 8f93852 Compare September 14, 2024 09:51
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 8f93852 to 16fed95 Compare October 2, 2024 16:27
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 16fed95 to ff9db27 Compare October 14, 2024 18:55
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from ff9db27 to e603572 Compare October 26, 2024 05:17
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from e603572 to c19de70 Compare October 28, 2024 14:44
@renovate renovate bot changed the title Update dependency vitest to v2 Update dependency vitest to v2 - autoclosed Nov 9, 2024
@renovate renovate bot closed this Nov 9, 2024
@renovate renovate bot deleted the renovate/major-vitest-monorepo branch November 9, 2024 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants