An E2E test for @clickhouse/client package beta version

[peter-leonov-ch]

Warning

DO NOT MERGE

This PR is not meant to be merged, it's an e2e test for the @clickhouse/client package release cycle

Why

HDX is a heavy CH JS client user. For the mutual benefit let's test CH JS releases as part of the CH JS QA process.

What

Bumping the client version and checking the CI checks.

CH JS team is going to update this PR with beta versions of CH JS package during the release cycle.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0334d2e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hyperdx-oss	Ready	Preview, Comment	Mar 9, 2026 2:21pm
hyperdx-v2-oss-app	Ready	Preview, Comment	Mar 9, 2026 2:21pm

[claude]

PR Review

✅ No critical issues found.

Notes:

• Dependency update from ClickHouse client ^1.12.1 → beta (1.16.0)
• Version jump: 1.12.1 → 1.16.0 (4 minor versions)
• No breaking API changes detected in HyperDX usage patterns
• Existing code uses stable APIs: createClient, query, format, query_params, etc.

Recommendations for testing:

• Ensure CI passes with full test suite (unit + integration tests)
• Verify query performance has not regressed
• Test both Node.js (packages/api) and browser (packages/app) ClickHouse clients
• Validate multi-tenant queries still filter correctly

Since this is a test PR for QA purposes, CI validation is the primary concern.

[github-actions]

E2E Test Results

✅ All tests passed • 86 passed • 3 skipped • 968s

Status	Count
✅ Passed	86
❌ Failed	0
⚠️ Flaky	2
⏭️ Skipped	3

Tests ran across 4 shards in parallel.

View full report →

[cursor]

Code Review

⚠️ Note: The PR description explicitly states DO NOT MERGE — this is an E2E compatibility test for the @clickhouse/client release cycle.

Changes reviewed: packages/common-utils/package.json and yarn.lock — bumping @clickhouse/client, @clickhouse/client-common, and @clickhouse/client-web from ^1.12.1 → beta (resolves to 1.18.2).

---

• ❌ "beta" is a floating dist-tag, not a pinned version → if/when merged to production, replace with an explicit version (e.g. "^1.18.2") to avoid surprise breakage from future beta publishes
• ⚠️ yarn.lock resolution looks correct (all three packages resolve to 1.18.2) — no mismatch issues

---

✅ No logic changes; the only code touched is the dependency version specifier and the generated lockfile. Acceptable as a temporary CI compatibility test PR as intended.

---