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

fix(renovate): Update dependency vitest to v2.1.8 #96

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

Conversation

darraghoriordan
Copy link
Owner

@darraghoriordan darraghoriordan commented Sep 15, 2024

This PR contains the following updates:

Package Type Update Change
vitest (source) dependencies minor 2.0.3 -> 2.1.8

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

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.4

Compare Source

   🚀 Features

This patch release includes a non-breaking feature for the experimental Browser Mode that doesn't follow SemVer. If you want to avoid picking up releases like this, make sure to pin the Vitest version in your package.json. See npm's documentation about semver for more information.

   🐞 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.

Potential Breaking Change
  • workspace:
    • Correctly resolve workspace globs and file paths  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6316 (afdcb)
    • This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)
    • For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.
    • This change doesn't affect non-glob usage.
   🚀 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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "* 0-3 * * *" in timezone Australia/Melbourne.

🚦 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 has been generated by Renovate Bot.

@darraghoriordan darraghoriordan changed the title fix(renovate): Update dependency vitest to v2.1.0 fix(renovate): Update dependency vitest to v2.1.1 Sep 17, 2024
@darraghoriordan darraghoriordan changed the title fix(renovate): Update dependency vitest to v2.1.1 fix(renovate): Update dependency vitest to v2.1.2 Oct 5, 2024
@darraghoriordan darraghoriordan changed the title fix(renovate): Update dependency vitest to v2.1.2 fix(renovate): Update dependency vitest to v2.1.3 Oct 17, 2024
@darraghoriordan darraghoriordan changed the title fix(renovate): Update dependency vitest to v2.1.3 fix(renovate): Update dependency vitest to v2.1.4 Oct 31, 2024
@darraghoriordan darraghoriordan changed the title fix(renovate): Update dependency vitest to v2.1.4 fix(renovate): Update dependency vitest to v2.1.5 Nov 16, 2024
@darraghoriordan darraghoriordan changed the title fix(renovate): Update dependency vitest to v2.1.5 fix(renovate): Update dependency vitest to v2.1.6 Nov 29, 2024
@darraghoriordan darraghoriordan changed the title fix(renovate): Update dependency vitest to v2.1.6 fix(renovate): Update dependency vitest to v2.1.8 Dec 5, 2024
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.

1 participant