Skip to content

Release HyperDX#2310

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

Release HyperDX#2310
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 19, 2026

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.4.2

Patch Changes

  • 19cd7c9: fix: only use pk and row uniqueness to look up a row
  • 8810ff0: feat: Add option for force-enabling/disabling text index support

@hyperdx/app@2.28.0

Minor Changes

  • 1df7583: feat: emit Lucene conditions from sidebar/dashboard filters to enable KV items direct_read optimization on Map columns

    Legacy type: 'sql' filters in URLs are automatically migrated to Lucene
    on page load. The persisted DashboardFilter.expression in MongoDB is unchanged.

Patch Changes

  • 937e043: fix: collapse duplicate map sub-key entries in the search filter sidebar (HDX-4340)

    A map sub-field stored in filterState under dot notation (e.g. LogAttributes.time,
    from a Lucene URL round-trip) and the same key returned by the facet query under
    bracket notation (e.g. LogAttributes['time']) no longer render as two separate
    accordion items. The merged entry keeps the bracket form so "Load more" stays
    valid, and the user's selection still resolves via a tolerant filterState lookup.

  • b94b8ef: fix: persist column widths in search results table

  • 19cd7c9: fix: only use pk and row uniqueness to look up a row

  • 8938b05: fix: let "Load more" surface unselected values in exact filter mode

  • 8810ff0: feat: Add option for force-enabling/disabling text index support

  • a8eb27d: feat: filters reflect all values, not search aware; filters use metadata MVs if available

  • Updated dependencies [d134212]

  • Updated dependencies [1df7583]

  • Updated dependencies [b30dfe0]

  • Updated dependencies [c3a8aa5]

  • Updated dependencies [8810ff0]

  • Updated dependencies [a8eb27d]

    • @hyperdx/api@2.28.0
    • @hyperdx/common-utils@0.20.0

@hyperdx/common-utils@0.20.0

Minor Changes

  • 1df7583: feat: emit Lucene conditions from sidebar/dashboard filters to enable KV items direct_read optimization on Map columns

    Legacy type: 'sql' filters in URLs are automatically migrated to Lucene
    on page load. The persisted DashboardFilter.expression in MongoDB is unchanged.

Patch Changes

  • b30dfe0: fix: support text index on lower(Body) with no preprocessor
  • 8810ff0: feat: Add option for force-enabling/disabling text index support
  • a8eb27d: feat: filters reflect all values, not search aware; filters use metadata MVs if available

@hyperdx/api@2.28.0

Patch Changes

  • d134212: feat(mcp): add hyperdx_describe_source tool and slim list_sources to catalog

    Add hyperdx_describe_source — returns full column schema, map attribute
    keys, and sampled low-cardinality values (SeverityText, StatusCode,
    ServiceName, etc.) for a single source. Uses existing rollup tables for
    performant value sampling.

    Slim hyperdx_list_sources to a lightweight MongoDB-only catalog (no
    ClickHouse queries). Source tools moved to a dedicated tools/sources/
    module.

    All query tool descriptions and prompts updated to reference the two-step
    list_sources → describe_source discovery workflow.

  • c3a8aa5: feat(mcp): rewrite dashboard authoring prompts and expose filters on hyperdx_save_dashboard

    The create_dashboard prompt now leads with a design checklist (alias every select item including number tiles, schema gap on groupBy so tables don't render arrayElement(SpanAttributes, '...') as the column header, RED columns with aliases, per-series numberFormat for durations, groupByColumnsOnLeft for inventory tables, dashboard-level filters instead of per-tile where literals, one-metric-per-tile for metric sources, required containers at five or more tiles, post-save validation of every tile, no title-recap markdown). The wall-of-JSON canonical example is gone; the dashboard_examples patterns carry the concrete shapes.

    The dashboard_examples set is replaced with four verified patterns (service_inventory, service_detail, log_analytics, backend_dependencies) plus the existing infrastructure_sql. Each non-SQL example leads with a "When to use" header and a "Why this shape" note so the model picks by intent, not by surface keyword match. Examples were built and rendered on a live dev stack before landing.

    The query_guide prompt gains a DASHBOARD FILTERS section that documents the filters: [{ type, name, expression, sourceId, where?, whereLanguage? }] shape, a NUMBER FORMAT section that explains the per-series vs. chart-level distinction, and a PER-TILE TYPE CONSTRAINTS note that metric tiles take exactly one select item per tile.

    hyperdx_save_dashboard now accepts filters on its input schema, reusing externalDashboardFilterSchemaWithId so the MCP and REST surfaces stay in lockstep and the existing convertExternalFiltersToInternal helper handles the conversion without translation. Filters round-trip through create, get, and update.

    Voice pass: every prompt string is now em-dash-free.

  • 8810ff0: feat: Add option for force-enabling/disabling text index support

  • a8eb27d: feat: filters reflect all values, not search aware; filters use metadata MVs if available

  • Updated dependencies [1df7583]

  • Updated dependencies [b30dfe0]

  • Updated dependencies [8810ff0]

  • Updated dependencies [a8eb27d]

    • @hyperdx/common-utils@0.20.0

@hyperdx/otel-collector@2.28.0

@vercel
Copy link
Copy Markdown

vercel Bot commented May 19, 2026

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

Project Deployment Actions Updated (UTC)
hyperdx-oss Ready Ready Preview, Comment May 22, 2026 7:11pm

Request Review

@github-actions github-actions Bot force-pushed the changeset-release/main branch from 14d6127 to ad88f40 Compare May 19, 2026 21:35
@github-actions github-actions Bot force-pushed the changeset-release/main branch from ad88f40 to 1477141 Compare May 20, 2026 14:28
@github-actions github-actions Bot force-pushed the changeset-release/main branch from 1477141 to efd4cd7 Compare May 20, 2026 14:53
@github-actions github-actions Bot force-pushed the changeset-release/main branch from efd4cd7 to 3482782 Compare May 20, 2026 16:16
@github-actions github-actions Bot force-pushed the changeset-release/main branch from 3482782 to a9c2676 Compare May 20, 2026 19:59
@github-actions github-actions Bot force-pushed the changeset-release/main branch from a9c2676 to 7167ac6 Compare May 21, 2026 15:20
@github-actions github-actions Bot force-pushed the changeset-release/main branch from 7167ac6 to d6c7094 Compare May 21, 2026 20:43
@github-actions github-actions Bot force-pushed the changeset-release/main branch from d6c7094 to 7db11bc Compare May 22, 2026 15:02
@github-actions github-actions Bot force-pushed the changeset-release/main branch from 7db11bc to 4b68fd7 Compare May 22, 2026 16:09
@github-actions github-actions Bot force-pushed the changeset-release/main branch from 4b68fd7 to 7c686ab Compare May 22, 2026 17:09
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.

0 participants