Skip to content

Releases: cloudflare/pint

v0.86.0

12 Jun 08:44
e622a47

Choose a tag to compare

Added

Changed

Fixed

  • Fixed false positive reports from promql/impossible
    when functions like abs(), clamp_min(), hour(), ln(),
    histogram_quantile(), or timestamp() wrap aggregations that already remove
    labels.
  • Fixed a crash in promql/aggregate when
    name regexp is not set.
  • Fixed alerts/template not populating
    $annotations map, causing template expansion to always return
    empty values for annotation references.
  • Fixed rule/label not matching regex key
    patterns on recording rules.
  • Fixed bare # pint disable promql/series comments having no effect
    on promql/series checks.
  • Fixed pint_rule_file_owner metric using symlink target path instead
    of symlink name, making it inconsistent with pint_problem metric.
  • Fixed swapped label name and URL in
    promql/vector_matching error message
    when both sides of a binary operation are missing a label.
  • Fixed false positive promql/range_query
    reports when Prometheus retention flag cannot be parsed.
  • Fixed promql/counter not checking bare
    counter metrics used without any wrapping function.

v0.85.0

04 Jun 14:48
16783c9

Choose a tag to compare

Added

  • Added promql/offset check that warns when a PromQL
    query uses an offset larger than configured Prometheus retention.
  • Added support for Prometheus v3.12.0 experimental PromQL functions:
    start(), end(), range(), step().

Changed

  • BitBucket reporter no longer creates Code Insight annotations.
    All problems are now reported as pull request comments.

Fixed

  • Fixed query/cost suggesting recording rules with
    incompatible label matchers.
  • Fixed query/cost suggesting recording rules when
    the query and recording rule use different aggregation grouping
    (e.g. sum by(job) vs sum without(instance)).

v0.84.0

22 May 14:53
08c3cbb

Choose a tag to compare

Added

  • GitHub and GitLab reporters will now automatically delete outdated general
    comments from previous pint ci runs.

Changed

  • Reported problems will now trim more parts of the query for which the problem is
    reported, to make it easier to read.
  • Reduced the number of low-value reports about smelly regexp selectors from the
    promql/regexp check.

v0.83.0

18 May 14:32
babfe4b

Choose a tag to compare

Added

  • rule/dependency check now supports ignoreGroupMismatch
    option for ignoring specific metrics when checking for cross-group
    dependencies - #1795.

Changed

  • Reported problems will now trim parts of the query for which the problem is reported
    to make it easier to read.

Fixed

  • GitHub and GitLab reporter was trying to create comments on incorrect lines.

v0.82.3

12 May 14:08
8a226a8

Choose a tag to compare

Fixed

  • Fixed incorrect reports from promql/regexp when empty match group is used.

v0.82.2

09 May 08:50
c4141b6

Choose a tag to compare

Fixed

  • rule/dependency won't report warnings when one
    query uses a recording rules that produce a static value (vector(1)).
    If the value is always the same the lag doesn't matter and it's a false positive.

v0.82.1

08 May 16:20
d147358

Choose a tag to compare

Fixed

  • GitHub and GitLab reporter was trying to create comments on unmodified files, which is not allowed.

v0.82.0

08 May 15:48
35da6e9

Choose a tag to compare

Changed

  • rule/dependency cross-group dependency check now
    only reports problems for recording rules.

Fixed

  • Fixed a panic when running pint ci.

v0.81.1

07 May 12:51
2a2e9d5

Choose a tag to compare

Fixed

  • Fixed GitLab reporter sending invalid line position when a comment is placed
    on a modified line in the diff, causing a 400 error from GitLab API.
  • GitHub and GitLab reporters will now correctly handle MRs between two feature branches.

v0.81.0

07 May 09:32
7cb671d

Choose a tag to compare

Changed

  • When running pint ci pint will now use git diff to calculate modified lines
    instead of git blame.
  • Broken symlinks and unreadable files in the rules directory are now reported
    as yaml/parse problems instead of causing a fatal error.

Fixed

  • Fixed parser not handling \r\n line endings correctly.
  • alerts/count check will now more accurately estimate alert counts.