Release HyperDX - #2975
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
5 times, most recently
from
August 24, 2026 22:32
03dffcd to
23f69d3
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 25, 2026 00:47
8bac8cd to
5ce4919
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/api@2.36.1
Patch Changes
@webhook-<id>mention strings and parsing them back out. That round-trip carried onlytypeandwebhookId, and it appended the channels after whatever the user wrote in the message body — so a body containingMAX_NOTIFICATIONS_PER_EVENTmentions consumed every slot of the per-event cap and the alert's own configured channel, the one target it was set up to notify, was silently never reached. Configured channels are now queued first and are exempt from that cap, which only ever meant to bound ad hoc mentions;channelsis already bounded byMAX_ALERT_CHANNELS. Mentions written into the message body are unchanged, still capped, and still deduplicated against the configured channels so naming one twice notifies it once. This also removes the lossiness that prevented a channel from carrying any field beyond its webhook id through to delivery, which downstream forks with richer channel types (e.g. anemailchannel, or a Slack-app channel that also needs a Slack channel id) could not work around.getDefaultExternalActionsis removed, as nothing needs the mention-string form of a configured channel any more.levelfield as a string enum so Gemini-backed clients can use the server at all.z.union([z.literal(0.5), ...])renders as{ "type": "number", "enum": [0.5, 0.9, 0.95, 0.99] }, and Gemini's function declarations only acceptenumalongsidetype: "string"— so a client that forwards MCP tool schemas to the provider had its entire tool list rejected because of this one field, surfacing as a generic "trouble connecting to the model provider" error that named neither the tool nor the property. Affectedclickstack_timeseries,clickstack_table,clickstack_save_dashboardandclickstack_patch_dashboard. Only the advertised wire type changes: numeric input is still accepted for callers working from a cached schema, the value is coerced back to a number before any consumer sees it, and out-of-set values are still rejected. The external REST API's ownlevelcontract is untouched. A new test asserts that no advertised tool schema carries a non-stringenumor an array-formitems, complementing the draft-2020-12 metaschema check.@hyperdx/app@2.36.1
Patch Changes
rr-web.offsetandrr-web.chunktiebreaks), chunks are reassembled by explicit chunk index per event, and dropped events are reported in the console and flagged with a warning indicator in the player instead of being swallowed. Existing recordings are replayed correctly without re-ingestion. Replaced replay streams are now also cancelled instead of streaming to completion in the background, and the player importsReplayerfrom@rrweb/replay(the replay-only package rrweb recommends over the deprecated combinedrrwebpackage).DashboardFiltersModalinto smaller components@hyperdx/common-utils@0.27.1
Patch Changes
@/*aliases leaking into the local type declarations@hyperdx/otel-collector@2.36.1