chore(deps-dev): bump vitest from 1.2.1 to 1.6.1 #7672
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
|
Hey there and thank you for opening this pull request! 👋 We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted. Your PR title is: Details: Unknown scope "deps-dev" found in pull request title "chore(deps-dev): bump vitest from 1.2.1 to 1.6.1". Scope must match one of: root, api-service, dashboard, inbound-mail, web, webhook, widget, worker, ws, ee-auth, ee-billing, ee-dal, ee-shared-services, ee-translation, application-generic, automation, dal, design-system, embed, api, notifications, novui, testing, client, framework, headless, js, nest, nextjs, node, notification-center, novu, providers, react, react-native, shared, stateless, nestjs, nextjs. |
✅ Deploy Preview for dev-web-novu ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
❌ Deploy Preview for dashboard-v2-novu-staging failed. Why did it fail? →
|
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/vitest-1.6.1
branch
from
cfe79c1 to
e3786c0
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/vitest-1.6.1
branch
from
e3786c0 to
5950273
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/vitest-1.6.1
branch
from
5950273 to
cdcc692
Compare
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 1.2.1 to 1.6.1. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.6.1/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/vitest-1.6.1
branch
from
cdcc692 to
34554be
Compare
Bumps vitest from 1.2.1 to 1.6.1.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
017e1eechore: release v1.6.17ce9fbbfix: backport #7317 to v1 (#7319)6b29f3dchore: release v1.6.0f8d3d22feat(benchmark): support comparing benchmark result (#5398)21e58bdfeat(browser): allow injecting scripts (#5656)30f728bfeat: custom "snapshotEnvironment" option (#5449)2f91322feat(reporter): supportincludeConsoleOutputandaddFileAttributein juni...c571276perf: unnecessary rpc call when coverage is disabled (#5658)bdce0a2feat: support standalone mode (#5565)40c299ffix: don't panic on empty files in node_modulesMaintainer changes
This version was pushed to npm by vitestbot, a new releaser for vitest 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.