Bump @vitest/coverage-istanbul from 1.0.2 to 1.3.0

[dependabot[bot]]

Bumps @vitest/coverage-istanbul from 1.0.2 to 1.3.0.

Release notes

Sourced from @​vitest/coverage-istanbul's releases.

v1.3.0

🚀 Features

• Deprecate watchExclude - by @​patak-dev in vitest-dev/vitest#5171 (82885)
• browser:
  • Run test files in isolated iframes - by @​sheremet-va in vitest-dev/vitest#5036 (4f401)
• config:
  • Add snapshotSerializers option - by @​fenghan34 in vitest-dev/vitest#5092 (5b102)
• reporters:
  • Support custom options - by @​AriPerkkio in vitest-dev/vitest#5111 (fec9c)
• runner:
  • Support automatic fixtures - by @​fenghan34 and @​sheremet-va in vitest-dev/vitest#5102 (0441f)
• ui:
  • Save splitpanes size to local storage - by @​posva in vitest-dev/vitest#5166 (c28b4)
• vitest:
  • Add onTestFinished hook - by @​sheremet-va in vitest-dev/vitest#5128 (6f5b4)
  • Add github actions reporter - by @​hi-ogawa in vitest-dev/vitest#5093 (40afb)
  • Expose jsdom global if jsdom environment is enabled - by @​sheremet-va in vitest-dev/vitest#5155 (567d2)
  • Add new CLI options - by @​sheremet-va in vitest-dev/vitest#5163 (4e179)
  • "test" accepts options object as the second parameter - by @​sheremet-va in vitest-dev/vitest#5142 (7d9b1)
• vm:
  • Support wasm module - by @​hi-ogawa in vitest-dev/vitest#5131 (5ed53)

🐞 Bug Fixes

• Fix sourcemap in vm pools - by @​hi-ogawa in vitest-dev/vitest#5063 (81105)
• Don't optimize react/jsx-runtime by default when running in Node - by @​sheremet-va in vitest-dev/vitest#5079 (0d2bf)
• Rpc timeout error messages to include caller - by @​AriPerkkio in vitest-dev/vitest#5103 (a6e04)
• Requires fixed version across the monorepo - by @​antfu in vitest-dev/vitest#5208 (68f51)
• Prevent merging of poolOptions - by @​penalosa in vitest-dev/vitest#5221 (bc5b2)
• browser:
  • Don't exclude node builtins from optimization - by @​sheremet-va in vitest-dev/vitest#5082 (714c9)
  • Support coverage.reportsDirectory with multiple directories - by @​AriPerkkio in vitest-dev/vitest#5056 (ae73f)
• cli:
  • Parse --browser=<name> correctly - by @​AriPerkkio in vitest-dev/vitest#5179 (656e2)
• coverage:
  • .tmp directory conflicts with --shard option - by @​AriPerkkio in vitest-dev/vitest#5184 (5749d)
• deps:
  • Update dependency strip-literal to v2 - by @​renovate[bot] in vitest-dev/vitest#5136 (ef557)
• reporters:
  • Testsuite name should include project root in Junit output - by @​fenghan34 in vitest-dev/vitest#5116 (2494f)
• typecheck:
  • Fix suite collection while-loop - by @​hi-ogawa in vitest-dev/vitest#5065 (35675)
• ui:
  • Fix tests duration time - by @​vovsemenv in vitest-dev/vitest#5219 (58103)
• utils:
  • Fix asymmetric matcher diff inside array - by @​hi-ogawa in vitest-dev/vitest#5189 (3ffcd)
• vitest:
  • Correctly report failed test files as failures in json reporter, export json reporter types - by @​sheremet-va in vitest-dev/vitest#5081 (0417b)
  • Don't run typecheck tests in browser if both are enabled - by @​sheremet-va in vitest-dev/vitest#5080 (1045b)
  • Handle function config inside defineWorkspace - by @​hi-ogawa in vitest-dev/vitest#5089 (0bf52)
  • Remove excessive listeners when running without isolation, don't reset the state - by @​sheremet-va in vitest-dev/vitest#5132 (b607f)
  • Auto-enable "github-actions" only where users didn't configure reporters - by @​hi-ogawa in vitest-dev/vitest#5158 (ef044)

... (truncated)

Commits

• bb2af3b chore: release v1.3.0
• 2ee2317 ci: add publish workflow (#5168)
• 68f5196 fix: requires fixed version across the monorepo (#5208)
• 5749d2c fix(coverage): .tmp directory conflicts with --shard option (#5184)
• 7a31a1a chore(deps): update dependency @​antfu/eslint-config to v2 (#5153)
• b1462a4 chore: release v1.2.2
• 6421c27 chore: release v1.2.1
• 4b41131 fix(coverage): thresholds.autoUpdate to work with arrow function configurat...
• b561c32 chore: release v1.2.0
• 96dc6e9 feat(coverage): custom reporter support (#4828)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by vitestbot, a new releaser for @​vitest/coverage-istanbul since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions

[tekton-robot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AlanGreene

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/tektoncd/dashboard/blob/main/OWNERS)~~ [AlanGreene] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment