Skip to content

Sync with upstream @hyperdx/app@2.45.0 (rebased) - #7

Open
mfroembgen wants to merge 14 commits into
mainfrom
fork-sync/app-2.45.0-rebase
Open

mfroembgen wants to merge 14 commits into
mainfrom
fork-sync/app-2.45.0-rebase

Conversation

@mfroembgen

@mfroembgen mfroembgen commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

Summary

The fork's main sat on @hyperdx/app@2.44.0 plus a fifth follow-up commit. This branch puts the same fork on upstream's latest release, @hyperdx/app@2.45.0 (0096a355c, also @hyperdx/api@2.45.0 and @hyperdx/otel-collector@2.45.0), as four patch commits. The E2E worker fix 97ee5727d is folded into the commit that owns the job-level E2E_WORKERS value.

Don't merge this with the PR button. Once it's reviewed, main gets force-pushed to this branch with a lease, and that needs Marco's confirmation.

 0096a355c  Release HyperDX (#3627)                                @hyperdx/app@2.45.0
 f83747032  fix: preserve JSON and Map search filter expressions   (was 4e0d28d84)
 c2b0bef38  feat: add WorkOS browser login and MCP OAuth            (was 4d77daed1)
 7171276f1  refactor: align fork runtime, tooling and dependencies (was 53c32707a)
+           + 97ee5727d ci: keep two E2E workers on fork pushes
+           + 2.45.0 adaptations (below)
 ed6ff75b9  build: preserve multi-architecture fork image packaging (was 4f1ffe94f)
-97ee5727d  ci: keep two E2E workers on fork pushes

Upstream 2.44.0 → 2.45.0 (10 commits):

Conflicts and adaptations (all in the runtime/tooling patch):

File Resolution
packages/{api,app,cli}/package.json Fork manifests (Bun, workspace:*) with upstream's 2.45.0 versions
yarn.lock Stays deleted (Bun); bun.lock locks hono 4.13.16 as upstream does
packages/api/src/routers/api/connections.ts Upstream's new z/objectIdSchema route validation through the fork's @/middleware/validation
packages/api/src/mcp/tools/query/helpers.ts Upstream dropped ClickHouseError; the type import comes from @clickhouse/client
packages/api/src/utils/clickhouseErrors.ts, timeseriesEngine.test.ts New upstream imports moved to @clickhouse/client (client-common doesn't resolve under the fork's Bun install)
packages/common-utils/src/__tests__/metadata.int.test.ts Upstream's TimeSeries ... version = 7 for ClickHouse 26.10 (the fork's CI already runs 26.10)
Upstream's new Jest tests (promqlBackend, promqlSources, connections, prometheus, connection, OnboardingModal, PromqlTableModelForm, useServiceMap) Converted to Vitest (vi.*, vi.importActual, MockInstance)
ServiceMapGroupByInput.tsx, OnboardingModal.test.tsx Accept undefined in the validator and assert lastCall, as the fork's react-hook-form 7.91/TS 6 types require
docker/clickhouse/local/init-db-e2e.sh Drop the fork's TimeSeries SETTINGS version = 2 pin: upstream's 2.45.0 seed writes the 26.10-default samples column (first CI run failed seeding with No such column samples in table default.e2e_promql)
docker/hyperdx/Dockerfile Fork packaging (already on ClickHouse 26.10.3.7)

Evidence

  • Before: after the replay, the API unit suite fails to import (Cannot find package '@clickhouse/client-common'), two useServiceMap tests fail with ReferenceError: jest is not defined, and app tsrs --noEmit reports 2 errors.
    After: locally with Bun 1.4.4: bun install --frozen-lockfile passes. Unit tests pass: api 88 files / 1597 tests, common-utils 46 / 3146, app 362 / 5595. tsrs --noEmit reports 0 errors in api and app, and eslint reports 0 errors in api, app and common-utils. Integration and E2E suites run in this PR's CI.

Merge Danger

Door: two-way

Landing this means force-pushing main from 97ee5727d7f0a252eace6f6db9cdf239f7cfa028 to ed6ff75b9f156db5a9f98a7e54428c089ea965f2. The old head stays reachable through fork-sync/app-2.44.0-rebase plus this record.

Blast Radius: fork-only

No images are published until someone runs fork-image.yml with publish=true. Consumers keep their current tags until they're updated.

karl-power and others added 14 commits November 12, 2026 08:54
## Summary

Upgrades ClickHouse from 26.8.36.3 to 26.10.3.7 and updates the tests that assumed the 26.8 TimeSeries layout. Needed for PromQL label lookups through ClickHouse's Prometheus HTTP API (26.9+).

- Pins `26.10.3.7` in the four compose files (incl. e2e) and the all-in-one `Dockerfile`.
- `metadata.int.test.ts`: pins the `getTimeSeriesTableColumns` tables to `version = 7` (26.10 defaults to version 8, which moves `min_time`/`max_time` out of the tags table), expects the renamed `metric_family` column, and adds `getTimeSeriesTableVersion` coverage.
- `timeseriesEngine.int.test.ts`: the version 8 suite fails instead of silently skipping.
- `seed-clickhouse.ts`: the e2e PromQL seed writes to `samples` (new tables have no `time_series` column).

No production code changes were needed. On an existing volume, `system.metric_log` history moves to `system.metric_log_0`. Local otel smoke tests need `clickhouse-client` 26.9+.

### References

- Linear Issue: part of HDX-5420
…ckHouse#3634)

## Summary

`clickstack_service_health` no longer tells the agent whether a service is critical, degraded or healthy. A healthy service used to get "report this service as steady, no action needed". That verdict comes from service-wide totals, so a regression confined to one endpoint, pod or attribute segment can sit under every threshold while the tool tells the agent to stop looking. In the `deploy-regression` eval, main calls the service with the bug "Healthy".

Each service now carries only evidence:

| | Before | After |
|---|---|---|
| Per-service field | `status: critical / degraded / healthy` | removed; `flags` and `score` stay |
| Summary, nothing crossed | `Healthy: … normal variance; report this service as steady, no action needed.` | `No metric crossed a threshold vs yesterday: error rate 0.50% vs 0.49%, p95 120ms vs 115ms, requests 3000 vs 2900.` |
| Summary, threshold crossed | `CRITICAL: error rate 8.00% vs 0.50%.` | `Crossed thresholds: error rate 8.00% vs 0.50%.` |
| Report summary | `statusCounts: {critical, degraded, healthy}` | `servicesFlagged` |
| Ordering | status, then new errors, then score | threshold-flagged services, then the rest; within each, new or growing errors first, then score |
| Span attributes | `mcp.service_health.critical_count`, `degraded_count` | `mcp.service_health.flagged_count` |

The tool description and `usage` now say that thresholds apply to service-wide totals and point to `clickstack_table` breakdowns before a service is ruled out. "No flags is a valid result for a routine check" stays, so status reports are not pushed into escalating.

`statusCounts` and per-service `status` are gone from the response. Both are MCP output read by agents; nothing else in the repo consumes them.

## Evals

A/B with `packages/hdx-eval`: branch (slot 99) vs `main` (slot 98), both built from `02f6fd060`, identical seeded data, `claude-opus-4-6`.

| Scenario | Runs/arm | Branch | Main | Δ | Tool calls (branch / main) |
|---|---|---|---|---|---|
| `service-health-check` | 3 | 76% | 75% | +1 | 7.7 / 5.7 |
| `error-root-cause` | 3 | 99% | 98% | +1 | 10.3 / 9.0 |
| `segmented-regression` | 8 | 75.5% | 71.6% | +3.9 | 14.9 / 17.1 |
| `deploy-regression` | 8 | 70.3% | 74.6% | −4.3 | 15.6 / 13.9 |
| `quiet-saturation` | 8 | 84.3% | 88.8% | −4.5 | 19.1 / 16.8 |
| **Average** | | **81.0%** | **81.6%** | **−0.6** | |

The change is neutral on scores. Per-run spread within an arm is 15–20 points, so no difference is significant (the largest has t ≈ 1); `segmented-regression` went from −11 after 3 runs to +13 over the next 5. Routine checks did not get more alarmist: the judge scored `service-health-check` 8 points higher on the branch. Its regex false-alarm checks scored it lower, but they mostly match negated phrases such as "not ongoing" and "not escalation-worthy". Agents make a few more tool calls in most scenarios once the tool stops saying "no action needed".

### How to reproduce

**Starting point:** local full stack (`yarn dev`) with trace data, and an MCP client such as `npx @modelcontextprotocol/inspector` connected to the local MCP endpoint (see `MCP.md`).

**On `main`:**

1. Call `clickstack_list_sources` and copy a `kind: "trace"` source ID.
2. Call `clickstack_service_health` with `{ "sourceId": "<id>" }`.
3. Each service has a `status`, and steady services read "Healthy: … no action needed."

**On this branch:**

1. Repeat the call.
2. There is no `status` field. Summaries state the crossed thresholds or the current vs comparison values, and `summary.servicesFlagged` replaces `statusCounts`.

### How to test on Vercel preview

N/A — non-UI change.

### References

- Linear Issue: HDX-5877
- Related PRs: ClickHouse#3411 (added `clickstack_service_health`)
…3639)

## Summary

`clickstack_save_webhook` and `clickstack_save_alert` now declare `openWorldHint: true`. Neither makes a network call during the tool call, but a saved webhook points at a third-party endpoint (Slack, incident.io, or any public URL with a templated body), and a saved alert sends requests to it on a schedule. Declaring them closed-world told MCP clients they could skip the extra review they give tools that reach outside the system. That review matters here: a prompt-injected agent could create a generic webhook to an attacker URL plus a frequently firing alert, and use them to exfiltrate telemetry.

Every other tool stays closed-world. `clickstack_delete_webhook` stays closed-world too, since deleting only stops deliveries. A new test pins the open-world set to exactly these two tools.

Flagged by an MCP tool-annotation compatibility check.

### How to reproduce

**Starting point:** local `yarn dev` (needs the API).

**On `main`:**

1. Call `tools/list` on the MCP server (`/api/mcp`).
2. `clickstack_save_webhook` and `clickstack_save_alert` report `annotations.openWorldHint: false`.

**On this branch:**

1. Same call: both report `openWorldHint: true`, and all other tools still report `false`.
2. `cd packages/api && yarn ci:unit src/mcp/__tests__/toolAnnotations.test.ts` passes.

### Notes

Committed with `--no-verify`. lint-staged passed. The hook's knip step fails on an issue already on `main`: `@opentelemetry/browser-sdk` is declared in `packages/app/package.json` (added in ClickHouse#3575) but never imported.
Bumps [hono](https://github.com/honojs/hono) from 4.13.13 to 4.13.16.
e notes</summary>
<p><em>Sourced from <a href="https://github.com/honojs/hono/releases">hono's releases</a>.</em></p>
<blockquote>
<h2>v4.13.16</h2>
<h2>Security fixes</h2>
<p>This release includes fixes for the following security issues:</p>
<h3><code>mount()</code> and <code>app.mount()</code> can forward a path that bypasses middleware scoped inside the mount prefix</h3>
<p>Affects: <code>mount()</code> in <code>hono/mount</code> and <code>app.mount()</code>. A dynamic prefix such as <code>/api/:tenant/*</code> was removed by the length of the route pattern. The forwarded path was also re-normalized by the URL parser, so a decoded <code>\</code> became <code>/</code> and <code>..</code> collapsed. Both let a crafted request skip middleware scoped inside the mount prefix. Routes such as <code>/assets*</code> and duplicate parameter names now throw. GHSA-4m76-xfj5-7975</p>
<h3>RegExpRouter skips wildcard middleware for certain route patterns and for paths with an encoded line terminator</h3>
<p>Affects: <code>RegExpRouter</code>, including the default <code>SmartRouter</code>. Wildcard middleware was not applied in three cases: a parameter written as <code>{[^/]+}</code> in the middleware path only, a <code>/prefix*</code> route next to <code>/prefix/*</code> middleware, and a path with an encoded line terminator. RegExpRouter now covers the same routes as the other routers. Custom patterns that can match the empty string, such as <code>{[0-9]*}</code>, throw <code>UnsupportedPathError</code>. Regenerate <code>PreparedRegExpRouter</code> data. GHSA-h7mg-cq63-vhpq</p>
<h3><code>validator('form')</code> skips validation for <code>multipart/form-data</code> requests with extra parameters</h3>
<p>Affects: <code>validator('form')</code> in <code>hono/validator</code>. A <code>multipart/form-data</code> request with an extra parameter such as <code>charset</code> was not recognized as a form. The validator then saw an empty object while the handler could read all fields. GHSA-4h7h-rv7c-7m2v</p>
<h3><code>css</code> helper does not escape a closing tag assembled from template parts and values, allowing HTML injection</h3>
<p>Affects: <code>css</code> in <code>hono/css</code>. A <code>&lt;/style&gt;</code> split between the template and a value, or between two values, was not escaped. Closing tags are now escaped after minification. GHSA-3gg2-335m-rxc6</p>
<h3><code>csrf()</code> does not check requests sent by hyperlink auditing (<code>text/ping</code>)</h3>
<p>Affects: <code>csrf()</code> in <code>hono/csrf</code>. A POST sent by Chromium's <code>&lt;a ping&gt;</code> has the content type <code>text/ping</code> and was not checked against <code>Origin</code> and <code>Sec-Fetch-Site</code>. GHSA-46wx-v44x-9hh2</p>
<hr />
<p>Users who rely on path-scoped middleware with <code>mount()</code>, wildcard middleware with the default router, <code>validator('form')</code>, the <code>css</code> helper with untrusted values, or <code>csrf()</code> are strongly encouraged to upgrade to this version.</p>
<h2>What's Changed</h2>
<ul>
<li>fix(jwt): reject a signature segment outside the base64url alphabet and a header with <code>crit</code> in <a href="https://redirect.github.com/honojs/hono/pull/5597">honojs/hono#5597</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/honojs/hono/compare/v4.13.15...v4.13.16">https://github.com/honojs/hono/compare/v4.13.15...v4.13.16</a></p>
<h2>v4.13.15</h2>
<h2>What's Changed</h2>
<ul>
<li>fix(auth): escape backslashes in the WWW-Authenticate realm by <a href="https://github.com/yusukebe"><code>@​yusukebe</code></a> in <a href="https://redirect.github.com/honojs/hono/pull/5590">honojs/hono#5590</a></li>
<li>docs(contributing): drop the note about linking a fork branch by <a href="https://github.com/yusukebe"><code>@​yusukebe</code></a> in <a href="https://redirect.github.com/honojs/hono/pull/5593">honojs/hono#5593</a></li>
<li>fix(context): allow <code>c.header()</code> after the response body is consumed by <a href="https://github.com/yusukebe"><code>@​yusukebe</code></a> in <a href="https://redirect.github.com/honojs/hono/pull/5587">honojs/hono#5587</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/honojs/hono/compare/v4.13.14...v4.13.15">https://github.com/honojs/hono/compare/v4.13.14...v4.13.15</a></p>
<h2>v4.13.14</h2>
<h2>What's Changed</h2>
<ul>
<li>docs(contributing): ask for issues instead of RPs <a href="https://redirect.github.com/honojs/hono/pull/5526">honojs/hono#5526</a></li>
<li>docs(readme): sync the contributing list with CONTRIBUTING.md <a href="https://redirect.github.com/honojs/hono/pull/5527">honojs/hono#5527</a></li>
<li>fix(adapters): accept Hono v5 prereleases in the <code>hono</code> peer range <a href="https://redirect.github.com/honojs/hono/pull/5537">honojs/hono#5537</a></li>
<li>chore: unified oxfmt and oxlint config <a href="https://redirect.github.com/honojs/hono/pull/5518">honojs/hono#5518</a></li>
<li>docs(readme): remove the deepwiki badge <a href="https://redirect.github.com/honojs/hono/pull/5548">honojs/hono#5548</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/honojs/hono/commit/c91b60a251186fb024557c6d55a11d8e388f179c"><code>c91b60a</code></a> 4.13.16</li>
<li><a href="https://github.com/honojs/hono/commit/e1dd58856eea8c3e91494ca6a12578325b01cf46"><code>e1dd588</code></a> fix(jwt): reject a signature segment outside the base64url alphabet and a hea...</li>
<li><a href="https://github.com/honojs/hono/commit/bf16471913b5199212dac33f5d170f94745dd26a"><code>bf16471</code></a> Merge commit from fork</li>
<li><a href="https://github.com/honojs/hono/commit/d88fab372415277a9e540e895650943dd08eef4a"><code>d88fab3</code></a> Merge commit from fork</li>
<li><a href="https://github.com/honojs/hono/commit/34f90432a1794b28e52802670efcd01963f716d6"><code>34f9043</code></a> Merge commit from fork</li>
<li><a href="https://github.com/honojs/hono/commit/8a103aa59bcfbffd5396b1548a0dff3688777c36"><code>8a103aa</code></a> Merge commit from fork</li>
<li><a href="https://github.com/honojs/hono/commit/15bbd96ad1b62a0b189db4fd8dc7bf8ef280c513"><code>15bbd96</code></a> Merge commit from fork</li>
<li><a href="https://github.com/honojs/hono/commit/3cb29de8f110654c37aa9b4c7eccdeae5254f5f2"><code>3cb29de</code></a> 4.13.15</li>
<li><a href="https://github.com/honojs/hono/commit/17ad0e21f5a91c939eeafa3df05793a8ea60f016"><code>17ad0e2</code></a> fix(context): allow <code>c.header()</code> after the response body is consumed (<a href="https://redirect.github.com/honojs/hono/issues/5587">#5587</a>)</li>
<li><a href="https://github.com/honojs/hono/commit/ee88684625077a2cd0e2f4613e593e2635ffe4c7"><code>ee88684</code></a> docs(contributing): drop the note about linking a fork branch (<a href="https://redirect.github.com/honojs/hono/issues/5593">#5593</a>)</li>
<li>Additional commits viewable in <a href="https://github.com/honojs/hono/compare/v4.13.13...v4.13.16">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=hono&package-manager=npm_and_yarn&previous-version=4.13.13&new-version=4.13.16)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will 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](https://github.com/ClickHouse/ClickStack/network/alerts).

</details>
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.


# Releases
## @hyperdx/api@2.45.0

### Minor Changes

- 2d17de5: feat: serve PromQL label lookups from ClickHouse's Prometheus HTTP API

  On ClickHouse 26.9+ with the `prometheus_api_v1` handler, `/labels` and `/label/:name/values` for a ClickHouse-backed PromQL source now proxy to the handler instead of querying the TimeSeries tags table with SQL. Older servers, servers without the handler, and sources set to `table-function` keep the SQL path, so a source that runs queries over HTTP on 26.6-26.8 still gets label autocomplete.

- db4e7ba: chore: upgrade bundled ClickHouse to 26.10.3.7

  The all-in-one image and the Docker Compose files now use
  `clickhouse/clickhouse-server:26.10.3.7-alpine`. New TimeSeries tables default
  to schema version 8, which keeps each series' time range in a separate inner
  table; existing tables keep their layout. `system.metric_log` switches to the
  bucketed schema, and rows from before the upgrade move to `system.metric_log_0`.

### Patch Changes

- c17fc16: fix: `{{note}}` in webhook bodies now contains the alert's note when the alert
  fires, not only in "Send test"
- 1fba1c3: fix: mark the MCP `clickstack_save_webhook` and `clickstack_save_alert` tools as open-world

  Saved webhooks and alerts send HTTP requests to third-party endpoints, so both tools now declare `openWorldHint: true`.

- 7b03880: feat: read the MCP PromQL label catalog from ClickHouse's Prometheus HTTP API

  `describe_source` on a ClickHouse-backed PromQL source now lists label and metric names through the `prometheus_api_v1` handler on ClickHouse 26.9+, and falls back to SQL on older servers, servers without the handler, and sources set to `table-function`.

- ac913ce: feat: Choose how a PromQL source on ClickHouse is evaluated (the Prometheus HTTP API or the `prometheusQuery` table functions) instead of probing the server on every query. Without a choice the server is still probed, but the answer is now kept for 5 minutes. A source set to the HTTP API against a server that does not serve it fails with a clear error. Onboarding pins a PromQL source it detects to the HTTP API when the server serves it.
- 7cfd333: fix(mcp): drop the health verdict from clickstack_service_health

  The tool no longer labels services critical, degraded or healthy, and no longer
  tells agents a service needs "no action". Each service keeps its threshold
  flags, score and a factual summary, so agents reason from the numbers instead of
  a verdict that service-wide totals can get wrong. `summary.statusCounts` is
  replaced by `summary.servicesFlagged`, and the span attributes
  `mcp.service_health.critical_count` and `mcp.service_health.degraded_count` are
  replaced by `mcp.service_health.flagged_count`.

- Updated dependencies [2d17de5]
- Updated dependencies [ac913ce]
  - @hyperdx/common-utils@0.35.0
## @hyperdx/app@2.45.0

### Minor Changes

- b3cbd02: feat: split the service map by up to 3 extra group-by SQL expressions (for
  example `ResourceAttributes['k8s.pod.name']`), so a node is a service plus
  those values and a slow or failing pod is no longer averaged into its service.

### Patch Changes

- ac913ce: feat: Choose how a PromQL source on ClickHouse is evaluated (the Prometheus HTTP API or the `prometheusQuery` table functions) instead of probing the server on every query. Without a choice the server is still probed, but the answer is now kept for 5 minutes. A source set to the HTTP API against a server that does not serve it fails with a clear error. Onboarding pins a PromQL source it detects to the HTTP API when the server serves it.
- Updated dependencies [c17fc16]
- Updated dependencies [1fba1c3]
- Updated dependencies [7b03880]
- Updated dependencies [2d17de5]
- Updated dependencies [ac913ce]
- Updated dependencies [7cfd333]
- Updated dependencies [db4e7ba]
  - @hyperdx/api@2.45.0
  - @hyperdx/common-utils@0.35.0
## @hyperdx/common-utils@0.35.0

### Minor Changes

- 2d17de5: feat: serve PromQL label lookups from ClickHouse's Prometheus HTTP API

  On ClickHouse 26.9+ with the `prometheus_api_v1` handler, `/labels` and `/label/:name/values` for a ClickHouse-backed PromQL source now proxy to the handler instead of querying the TimeSeries tags table with SQL. Older servers, servers without the handler, and sources set to `table-function` keep the SQL path, so a source that runs queries over HTTP on 26.6-26.8 still gets label autocomplete.

### Patch Changes

- ac913ce: feat: Choose how a PromQL source on ClickHouse is evaluated (the Prometheus HTTP API or the `prometheusQuery` table functions) instead of probing the server on every query. Without a choice the server is still probed, but the answer is now kept for 5 minutes. A source set to the HTTP API against a server that does not serve it fails with a clear error. Onboarding pins a PromQL source it detects to the HTTP API when the server serves it.
## @hyperdx/otel-collector@2.45.0
Folds b1a4d7b (replayed on 2.43.1 as 1dcae2b).

On 2.44.0 the e2e ClickHouse seed keeps upstream's `@request_id` JSON
key next to the typed JSON fields this fix tests.
Folds 122b942 (replayed on 2.43.1 as 43388c2) and the WorkOS parts of
the 2.44.0 sync (#5).

On 2.44.0:
- Member removal keeps upstream's org API keys and last-member guard.
  With WorkOS it unsets the team and rotates the access key, and a
  restore after a race puts both back. Members without a team cannot
  authenticate with an access key.
- OAuth credential scrubbing moves from the HyperDX SDK tracing preload
  into upstream's ClickStack telemetry preload.
- The WorkOS removal tests keep a second member, since the last member
  can never be removed.
Folds 9f10846 (replayed on 2.43.1 as e01f52b) and the 2.44.0
adaptations from #5:
- run upstream's new and changed tests on Vitest;
- adapt upstream code to Mongoose 9, Zod 4, Express 5 validation and
  @clickhouse/client, and lock upstream's new dependencies;
- pin @opentelemetry/api 1.9.1, the range the ClickStack SDKs accept;
- run the ClickStack telemetry preload under Bun, keeping HTTP server
  spans when HTTPS loads after HTTP;
- import the undici package so Bun keeps upstream's webhook DNS check;
- move upstream's uplot patch to Bun patches and drop the @hyperdx/browser
  patch, which the ClickStack browser SDK supersedes, with the browser SDK
  memory proof ported to it.

Also folds 97ee572: the E2E Playwright step no longer overrides the
job-level fork E2E_WORKERS value of two, so pushes to main stop running
four workers on the 4-vCPU runner.

On 2.45.0:
- run upstream's new PromQL, connection, onboarding and service-map
  tests on Vitest;
- import ClickHouseError from @clickhouse/client in the new
  utils/clickhouseErrors.ts;
- accept an unset value in the service-map group-by validator, as the
  fork's react-hook-form types require;
- keep upstream's TimeSeries version 7 test tables and default E2E
  PromQL table (its `samples` column) for ClickHouse 26.10;
- lock hono 4.13.16, as upstream does.
Folds the packaging commit of the 2.43.1 release stack (87ec1b5),
unchanged on 2.44.0.
@mfroembgen
mfroembgen force-pushed the fork-sync/app-2.45.0-rebase branch from 7525e69 to ed6ff75 Compare November 16, 2026 08:23
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.

5 participants