Release HyperDX - #2919
Open
github-actions[bot] wants to merge 2 commits into
Open
Conversation
Contributor
|
PR author is in the excluded authors list. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
August 17, 2026 16:39
4d7d4be to
9484211
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
11 times, most recently
from
August 19, 2026 12:06
eb87815 to
4364833
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 19, 2026 14:21
b1ea9ef to
d69c714
Compare
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.
This PR was opened by the Changesets release 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/common-utils@0.27.0
Minor Changes
formulason builder chart configs) in the composed multi-series metric query. Letter-ref expressions likeA / (A + B + C) * 100compile into the final SELECT projection over the pivoted per-series columns, with ratio-consistent missing-data semantics: a missing operand counts as 0 while a zero or missing division denominator yields NULL (a rendered gap).showOperandSeries: falseemits only the formula column(s). Works for grouped and ungrouped line, table, and number charts, and single-series charts with a formula now route through the composed query path.$__sourceTable(<metricType>)macro per series branch, instead of returning a "cannot be auto-converted" error. Non-time-series metric charts remain unsupported, matching the existing single-series restriction.Patch Changes
"Edit alert" action opens a modal for changing the alert's threshold,
evaluation interval, schedule, group-by (saved-search alerts), notification
webhook, and note, and a Delete action (with confirmation) removes the alert
and returns to the alerts list. Alert API responses now include the
notification channel's webhook id and the alert's name/message template so
edits round-trip these fields.
queries (KV rollup and map text-index lookups) previously bound one query
parameter per key; with ~100 keys this exceeded the ClickHouse web client's URL
parameter budget, silently promoting the request to a multipart/form-data body
that proxy gateways can reject — every LowCardinality-column and map-attribute
filter then vanished without an error. Keys are now inlined as SQL-escaped
literals so the query rides the POST body with a constant parameter count. Also
fixes an operator-precedence bug that applied the KV rollup time filter (and
notEmpty guard) to only the last OR branch.
colorRulesbetweenrule declared itsvalueas a Zod tuple, whichzod-to-json-schemarenders in the draft-07 tuple form (items: [ ... ]). Draft 2020-12 requiresitemsto be a schema rather than an array, soclickstack_save_dashboardandclickstack_patch_dashboardfailed validation — and clients that forward MCP tool schemas straight to an LLM provider (e.g. the Anthropic API) rejected the entire tool list withtools.N.custom.input_schema: JSON schema is invalid, making the MCP server unusable.valueis now a fixed-length array, which validates identically and serializes to the same[min, max]wire format. A new test validates every MCP tool's input schema against the 2020-12 metaschema so this cannot regress.use_variant_as_common_typesetting. As a defensive layer, all-numericVariant(...)result columns (e.g. from raw-SQL charts) are now also classified as numeric.@hyperdx/api@2.35.1
Patch Changes
"Edit alert" action opens a modal for changing the alert's threshold,
evaluation interval, schedule, group-by (saved-search alerts), notification
webhook, and note, and a Delete action (with confirmation) removes the alert
and returns to the alerts list. Alert API responses now include the
notification channel's webhook id and the alert's name/message template so
edits round-trip these fields.
colorRulesbetweenrule declared itsvalueas a Zod tuple, whichzod-to-json-schemarenders in the draft-07 tuple form (items: [ ... ]). Draft 2020-12 requiresitemsto be a schema rather than an array, soclickstack_save_dashboardandclickstack_patch_dashboardfailed validation — and clients that forward MCP tool schemas straight to an LLM provider (e.g. the Anthropic API) rejected the entire tool list withtools.N.custom.input_schema: JSON schema is invalid, making the MCP server unusable.valueis now a fixed-length array, which validates identically and serializes to the same[min, max]wire format. A new test validates every MCP tool's input schema against the 2020-12 metaschema so this cannot regress.@hyperdx/app@2.35.1
Patch Changes
"Edit alert" action opens a modal for changing the alert's threshold,
evaluation interval, schedule, group-by (saved-search alerts), notification
webhook, and note, and a Delete action (with confirmation) removes the alert
and returns to the alerts list. Alert API responses now include the
notification channel's webhook id and the alert's name/message template so
edits round-trip these fields.
Render
<Context>directly instead of<Context.Provider>, use theusehookinstead of
useContext, and passrefas a regular prop instead of wrappingcomponents in
forwardRef. The corresponding@eslint-react/no-context-provider,no-use-context, andno-forward-refrules are promoted toerrorand theapp's
--max-warningsceiling is lowered. Behavior is unchanged.use_variant_as_common_typesetting. As a defensive layer, all-numericVariant(...)result columns (e.g. from raw-SQL charts) are now also classified as numeric.ChartCardcomponent that gives standalone charts the samecard treatment as custom dashboard tiles (bordered surface + full-bleed header
divider). The card header stays pinned while the card body scrolls (e.g. cards
wrapping a long list like "Top 20 Most Time Consuming Queries"): in card mode
the header is a fixed row and scrollable list content gets its own internal
scroll region, so the header no longer scrolls away once you pass the first
card-height of content. Migrate the Service
Dashboards (HTTP, Database, Errors, endpoint and DB-query side panels) and the
ClickHouse page from the old
ChartBoxwrapper toChartCardso chart surfaceslook consistent across the app.
@hyperdx/otel-collector@2.35.1