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

chore(deps): update vitest monorepo to v2.1.3 #557

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 8, 2024

This PR contains the following updates:

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

Release Notes

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

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

v2.0.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.0.2

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

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 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 changed the title chore(deps): update vitest monorepo to v2.0.1 chore(deps): update vitest monorepo to v2.0.2 Jul 10, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 58bf6d4 to 5da02d3 Compare July 15, 2024 10:48
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.0.2 chore(deps): update vitest monorepo to v2.0.3 Jul 15, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 5da02d3 to 5b74c85 Compare July 22, 2024 11:02
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.0.3 chore(deps): update vitest monorepo to v2.0.4 Jul 22, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 5b74c85 to 87d1c81 Compare July 31, 2024 11:07
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.0.4 chore(deps): update vitest monorepo to v2.0.5 Jul 31, 2024
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.0.5 chore(deps): update vitest monorepo to v2.1.0 Sep 12, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from e76b706 to 8996117 Compare September 13, 2024 15:51
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.0 chore(deps): update vitest monorepo to v2.1.1 Sep 13, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 8996117 to 306d270 Compare October 2, 2024 17:05
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.1 chore(deps): update vitest monorepo to v2.1.2 Oct 2, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 306d270 to e335964 Compare October 9, 2024 11:54
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.2 chore(deps): update vitest monorepo to v2.1.3 Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants