v5.55.1-rc.1
Pre-release
Pre-release
Immutable
release. Only release title and notes can be modified.
v5.55.0 - 2026-05-21
Added
- Show the configured date below the source name in the metrics table for calendar date sources, so the date is visible when the metric is collapsed. Closes #11143.
- When measuring outdated dependencies with pip as source, allow for filtering major, minor, or patch updates. Closes #12979.
- When using Grafana k6 summary.json as source for the 'source version' metric, also accept the snake case
k6_versionkey as written by k6 v1.7.x, in addition to the camel casek6Versionkey specified by the schema. Closes #13243. - When using Grafana k6 summary.json as source for the 'source up-to-dateness' metric, also accept the snake case
generated_atkey as written by k6 v1.7.x, in addition to the camel casegeneratedAtkey specified by the schema. Closes #13276.
Removed
- Remove the feature to mass edit source parameters of sources with the same type in a metric, in a subject, or in all reports. This prepares for the introduction of source locations as objects separate from sources. Source location parameters (URLs and credentials) can still be changed for sources with the same type in a report via the "Sources" tab in the report title. Closes #13153.
- Removed the "v"-prefix from the Helm chart version number to comply with SemVerV2 enforced by the Helm linter. Closes #13246.
Fixed
- The documentation on importing reports was claiming that a report with credentials can only be re-imported into the same Quality-time instance. This is no longer true since v5.52.0. Fixes #13080.
- When a metric had multiple sources where one source was created by copying another, the copied source's entity user data (such as suppressed violation statuses) was overwritten with the original source's user data on every measurement, causing suppressed violations to revert to "unconfirmed". Fixes #13275.
Deprecated
- Support for Pyupio Safety as source for metrics is deprecated and marked for removal in the future, because Quality-time only supports v1 of the Safety JSON output and upgrading to v3 is blocked. Closes #13077.