Repository navigation
deps(sdk): bump the sdk-deps group in /clients/ts with 2 updates - #103
Merged
github-actions[bot] merged 1 commit intoMay 11, 2026
Merged
github-actions[bot] merged 1 commit into
github-actions[bot] merged 1 commit into
Conversation
Bumps the sdk-deps group in /clients/ts with 2 updates: [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `@vitest/coverage-v8` from 4.1.5 to 4.1.6 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.6/packages/coverage-v8) Updates `vitest` from 4.1.5 to 4.1.6 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.6/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.6 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: sdk-deps - dependency-name: vitest dependency-version: 4.1.6 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: sdk-deps ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
dependabot
Bot
deleted the
dependabot/npm_and_yarn/clients/ts/sdk-deps-5b3ec22b96
branch
May 11, 2026 19:51
4 of 6 tasks
EricAndrechek
added a commit
that referenced
this pull request
May 19, 2026
…#165) Closes #160. ## Summary - All three TS workspaces (`clients/ts`, `tests/e2e/sdk`, `docs`) plus the `setup-env` composite action jump from `pnpm@10.33.0` → `pnpm@11.1.3`. - pnpm 11 deprecates the `pnpm` field in `package.json` — `onlyBuiltDependencies` moves into a new `pnpm-workspace.yaml` next to each `package.json` and is renamed to `allowBuilds:` with the new map-of-booleans syntax. - Same `pnpm-workspace.yaml` files set `minimumReleaseAge: 10080` (7 days) so pnpm refuses freshly published packages until npm/jsr have had a week to flag a compromised release. - New repo-root `.nvmrc` pins Node 22 LTS — matches what CI's `setup-node` already uses, and reduces Node-major-surprise risk on `nvm`/`fnm`/`volta` dev machines. - README, AGENTS.md, and `docs/development.md` updated for the new versions. ## Notes from investigation The issue flagged two open questions; here's where I landed on each: - **`electron-winstaller` mystery.** Not a hidden transitive of any WaveHouse workspace. The pnpm 11 ignored-build warning came from a stray `/Users/eric/pnpm-workspace.yaml` in the local dev's home directory — pnpm 11 walks up the directory tree looking for a workspace root and found it before the in-repo one. Correctly omitted from `allowBuilds`. (Future devs hitting this should clean up their home dir or rename their stray workspace file.) - **Node 26 Vitest crash.** I could not reproduce it on the current branch — `make test-sdk` runs all 120 tests cleanly on Node 26. The earlier `clients/ts` bump to `vitest@^4.1.6` (PR #103) seems to have already absorbed the V8 incompatibility. I still added the `.nvmrc` per the issue's request, since pinning has independent value and the cost is one line. ## Test plan - [x] `make build-sdk` — green - [x] `make build-docs` — green - [x] `make test-sdk` — 120/120 passed on Node 26 + pnpm 11 - [x] `pnpm install --frozen-lockfile` clean in all three workspaces (CI's path) - [ ] CI green on this PR (full `make ci` including `make test-e2e` which needs the containerized ClickHouse + wavehouse binary) - [ ] Re-validate PR #147's pre-push gate flow once this lands, per the issue's "Related" section 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated pnpm to 11.1.3 and pinned Node.js to 22 LTS across the repo. * Added/updated per-workspace pnpm settings to allow native build steps and enforce a 7-day minimum release age for packages. * **Documentation** * Updated README, development guide, and prerequisites docs to reflect Node.js 22 LTS and pnpm 11.1.3 requirements and verification instructions. <!-- review_stack_entry_start --> [](https://app.coderabbit.ai/change-stack/Wave-RF/WaveHouse/pull/165?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack) <!-- review_stack_entry_end --> <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
](https://app.coderabbit.ai/change-stack/Wave-RF/WaveHouse/pull/165?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack){kind=link}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the sdk-deps group in /clients/ts with 2 updates: @vitest/coverage-v8 and vitest.
Updates
@vitest/coverage-v8from 4.1.5 to 4.1.6Release notes
Sourced from @vitest/coverage-v8's releases.
Commits
a8fd24cchore: release v4.1.6Updates
vitestfrom 4.1.5 to 4.1.6Release notes
Sourced from vitest's releases.
Commits
a8fd24cchore: release v4.1.618af98cfix(browser): simplify orchestrator otel carrier (#10285)3188260feat(browser): provide project reference inToMatchScreenshotResolvePath(#...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 <dependency name> major versionwill 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 <dependency name> minor versionwill 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 <dependency name>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 <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions