Releases: cloudflare/pint
Releases · cloudflare/pint
v0.77.0
Added
-
The promql/impossible check will now warn about aggregations and
and binary operations that try to operate on labels that are already removed in the query.
Example:- record: foo expr: sum(foo) / on(cluster) sum(bar)
The above tries to join two series on the
clusterlabel, butsum(...)already removed labels
from the results on both side, so there will be no such label on join on. -
The promql/impossible check will now warn about label joins
usinggroup_left(...)andgroup_right(...)that are not possible or not used in any way.
Fixed
- For queries using binary expressions between two vectors Prometheus will remove the metric name
from resulting series, pint will now also apply the same logic when checking queries.
v0.76.1
Fixed
- CI comments would sometimes print the problematic query fragment twice.
v0.76.0
Added
- Added support for
toDurationandnowtemplate functions added in Prometheus v3.6.
Fixed
- Some checks would fail to run queries against Prometheus servers if the query had comments in it.
v0.75.0
Added
- Added promql/selector check - #1416
and #1540.
v0.74.8
Fixed
- Fixed incorrect suggestions from query/cost for function calls with different arguments.
v0.74.7
Fixed
- Fixed a bug in GitLab integration causing problems fail to create comments when they are reported on deleted lines.
- Fixed incorrect suggestions from query/cost for rules joining on multiple metrics.
v0.74.6
Fixed
- Fixed a bug in GitLab integration causing some problems fail to create comments when files were renamed and modified.
v0.74.5
Fixed
- Fixed incorrect incorrect suggestions generated by query/cost check.
- Fixed unmodified lines incorrectly marked as modified when running
pint ci.
v0.74.4
Fixed
- Fixed false positive reports from promql/rate check when native histograms or summaries are used.
v0.74.3
Fixed
- Fixed false positive reports from promql/fragile check - #1466.
- Fixed incorrect reports from query/cost when multiple rules with
rate(...)were present
and each had a different rate time window.