Skip to content

Conversation

@peter-leonov-ch
Copy link

Warning

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

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 / release versions of CH JS package before / during the release cycle.

@changeset-bot
Copy link

changeset-bot bot commented Jan 5, 2026

⚠️ No Changeset found

Latest commit: a465b8e

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
Copy link

vercel bot commented Jan 5, 2026

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

Project Deployment Review Updated (UTC)
hyperdx-v2-oss-app Ready Ready Preview, Comment Jan 7, 2026 10:27am

@claude
Copy link

claude bot commented Jan 5, 2026

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
Copy link
Contributor

github-actions bot commented Jan 5, 2026

E2E Test Results

All tests passed • 56 passed • 4 skipped • 723s

Status Count
✅ Passed 56
❌ Failed 0
⚠️ Flaky 0
⏭️ Skipped 4

Tests ran across 4 shards in parallel.

View full report →

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants