chore(deps-dev): bump vitest from 4.1.10 to 4.1.11 in /examples/next/websockets - #2254
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.10 to 4.1.11. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.11/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.11 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| "typescript": "^6.0.3", | ||
| "vite": "^8.1.0", | ||
| "vitest": "4.1.10", | ||
| "vitest": "4.1.11", |
There was a problem hiding this comment.
🟡 Frozen dependency install fails
A frozen pnpm install rejects vitest@4.1.11 because the workspace importer still specifies 4.1.10. CI exits before builds or tests run.
Learn more
The repository uses one workspace lockfile. Each workspace importer records the dependency specifier from its manifest and the exact resolved package graph. The install action runs pnpm install --frozen-lockfile, which refuses to regenerate an importer whose manifest changed. This PR changes the WebSockets example's Vitest specifier without updating that importer, so dependency installation stops before CI reaches its checks.
Example: On this commit, the manifest requests vitest: 4.1.11, while the examples/next/websockets importer records specifier: 4.1.10 and resolves Vitest 4.1.10. A frozen install rejects this mismatch instead of installing 4.1.11.
Recommended fix: Run pnpm install with pnpm 11.9.0 and commit the regenerated pnpm-lock.yaml. Verify that the WebSockets importer and Vitest 4.1.11 package graph are updated.
Was this helpful? React with 👍 or 👎 to provide feedback.
Bumps vitest from 4.1.10 to 4.1.11.
Release notes
Sourced from vitest's releases.
Commits
9bd8d46chore: release v4.1.11 (#10995)9851dbcfix(browser): trigger playwright/chromium gc on lower disk availability [back...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 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.