v0.9.4

Released at 2026-07-03

Update Note 1: cluster version: this release bumps the internal vtselect and vtstorage protocol version (see the queries-longer-than-10MB fix in VictoriaLogs #1462). Any version mismatch between vtselect and vtstorage will cause requests to fail, meaning queries will error out during a rolling upgrade when the cluster runs mixed component versions. All components must be upgraded if you want to upgrade to this release or later.

• SECURITY: upgrade Go builder from Go1.26.3 to Go1.26.4. See the list of issues addressed in Go1.26.4.

• FEATURE: logstorage: upgrade VictoriaLogs dependency from v1.50.0 to v1.51.0.

• FEATURE: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: support configuring max traces limit for Jaeger and Tempo search traces APIs. Previously each API has default limit 20, and a hardcoded limit 1000 to prevent users from requesting an excessively large limit query argument.

• FEATURE: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: unify the command-line flags for configuring the maximum tags limit used in tags (tag values), service name, and span name search APIs with -search.maxTags. The old flags -search.traceMaxServiceNameList and -search.traceMaxSpanNameList are now deprecated.

• BUGFIX: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: return intrinsic span fields (name, kind, status, duration) under the intrinsic scope of the Tempo /api/v2/search/tags endpoint, and support scope=intrinsic. Previously these fields were missing (they have no attribute prefix and were skipped during tag discovery, and scope=intrinsic returned an error), so they did not appear in the Grafana Traces Drilldown attribute breakdown. Thank @vshulakov-sh for the pull request #175.

• BUGFIX: Single-node VictoriaTraces and vtselect in VictoriaTraces cluster: return proper spans with within spanSets for the Tempo /api/search API. Previously, this API only returned root spans. This enables trace span focus by span ID when viewing a trace. See the pull request #201 for details. Thank @yusufcemalcelebi for reporting the issue and proposing the change.