Skip to content

Bump the npm_and_yarn group across 2 directories with 1 update #275

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.

Sign up for GitHub

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

Merged
mishushakov merged 1 commit into from
Jun 1, 2026
Merged

Bump the npm_and_yarn group across 2 directories with 1 update #275

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion js/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@
"npm-check-updates": "^17.1.14",
"tsup": "^8.5.1",
"typescript": "^5.5.3",
"vitest": "^3.2.4"
"vitest": "^4.1.0"

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 1, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Move worker limits out of poolOptions

Upgrading to Vitest 4 makes the existing concurrency cap in js/vitest.config.mts ineffective: the Vitest 4 migration guide says poolOptions was removed and maxThreads/maxForks were replaced by top-level maxWorkers. Because the sandboxTest fixture creates a real sandbox for tests, pnpm test can now fan out to Vitest's default worker count instead of the intended max of 4, which can overload the sandbox service or exhaust quotas in CI. Please migrate that config to top-level minWorkers/maxWorkers (or the intended Vitest 4 equivalent) as part of this bump.

Useful? React with 👍 / 👎.

},
"files": [
"dist",
Expand Down
Loading
Loading