Release HyperDX - #2854
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
11 times, most recently
from
August 11, 2026 17:32
e1a4f87 to
c00a8a3
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 11, 2026 17:52
bd1d51b to
cb1bfdd
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/cli@0.6.1
Patch Changes
query, sources/connections/dashboards, auth, team, upload-sourcemaps) ahead of
launch, so npm and GitHub show everything the CLI can do. Also remove a stale
reference to the removed
hdx streamcommand fromhdx chart --help.@hyperdx/api@2.35.0
Minor Changes
ERROR-state AlertHistory records instead of only a latest-only snapshot,
upserted per evaluation window so retries collapse into a single row. Query
timeouts are classified separately (QUERY_TIMEOUT, including timeouts wrapped
by the ClickHouse query client) with an actionable message. ERROR rows are
excluded from scheduling/backfill computations so failed windows are still
retried and backfilled, and once a failed window recovers (via a same-window
retry or a later tick's backfill) its stale ERROR row is removed. Evaluation
analytics (query/webhook durations, backfilled buckets) are recorded on every
history row.
endpoint: per-window evaluation history scoped to a time range (clamped to the
retention window) with per-group breakdown for group-by alerts, evaluation
analytics fields, deduped error surfacing for ERROR-state windows, and
cursor-based pagination that always advances across gaps. Adds read-side
schema/type support for ERROR-state AlertHistory rows and evaluation analytics.
Patch Changes
clients can distinguish read-only query tools from mutating ones. Read/query
tools are marked read-only; save/patch and delete tools are marked destructive
since they can overwrite or remove existing resources. Hints that would be
redundant against the MCP spec defaults are omitted (e.g. destructiveHint is
left off read-only tools, where it has no meaning).
connection.
@hyperdx/common-utils@0.26.0
Minor Changes
ERROR-state AlertHistory records instead of only a latest-only snapshot,
upserted per evaluation window so retries collapse into a single row. Query
timeouts are classified separately (QUERY_TIMEOUT, including timeouts wrapped
by the ClickHouse query client) with an actionable message. ERROR rows are
excluded from scheduling/backfill computations so failed windows are still
retried and backfilled, and once a failed window recovers (via a same-window
retry or a later tick's backfill) its stale ERROR row is removed. Evaluation
analytics (query/webhook durations, backfilled buckets) are recorded on every
history row.
endpoint: per-window evaluation history scoped to a time range (clamped to the
retention window) with per-group breakdown for group-by alerts, evaluation
analytics fields, deduped error surfacing for ERROR-state windows, and
cursor-based pagination that always advances across gaps. Adds read-side
schema/type support for ERROR-state AlertHistory rows and evaluation analytics.
Patch Changes
b9430a6: feat: Add broadcast and variable settings to dashboard filters
2d33b83: Escape the Map subscript once in numeric and Bool field searches
The three equality branches for
Booland numeric value types escaped thecolumn expression as an identifier even when it was already a rendered map
subscript, so
Measures.latency_ms:250wrapped`Measures`['latency_ms']in a second layer of backticks that ClickHouse reads as one identifier rather
than a map lookup. Quoting the term worked around it for numeric maps; for
Map(String, Bool)columns both spellings were affected.@hyperdx/otel-collector@2.35.0
Minor Changes
OTLP_AUTH_TOKEN. SetOIDC_ISSUER_URLandOIDC_AUDIENCEto validate incoming OTLP requests against an OIDC provider's published JWKS instead of a single long-lived shared secret.@hyperdx/app@2.35.0
Patch Changes
endpoint: per-window evaluation history scoped to a time range (clamped to the
retention window) with per-group breakdown for group-by alerts, evaluation
analytics fields, deduped error surfacing for ERROR-state windows, and
cursor-based pagination that always advances across gaps. Adds read-side
schema/type support for ERROR-state AlertHistory rows and evaluation analytics.
@hyperdx/hdx-eval@0.3.2
Patch Changes