NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #1789 by repository stars
Last release 3 days ago
02 Oct 2026
Ships on a steady schedule
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
401 releases · first in 2021
One column per quarter.
Nothing published for this version
Nothing published for this version
Fixed false positive reports from promql/fragile check - #1466.
rate(...) were present
and each had a different rate time window.Fixed an issue where pint would fail to create an MR comment if GitLab API returned empty diff body.
Fixed incorrect suggestion from query/cost when a query uses joins or unless.
promql/fragile check will now warn about alerting rules using aggregations that might cause false positives when Prometheus restarts.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fixed a bug in GitLab integration causing incorrect line numbers to be used for comments.
Nothing published for this version
Fixed a bug in GitLab integration causing some problems to fail to create comments when files were renamed.
Nothing published for this version
Fixed incorrect error message for some problems reported by alerts/template check.
Fixed handling of resolved comments when using GitLab with pint ci command.
pint ci command.Fixed incorrect value in This pint run would create N comment(s), which is more than the limit ... comments when using GitHub or GitLab with pint ci c
This pint run would create N comment(s), which is more than the limit ... comments
when using GitHub or GitLab with pint ci command.Fixed handling of stale comments when using GitLab with pint ci command.
pint ci command.Fixed relaxed parsing mode not finding all rules in some files - #1405.
relaxed parsing mode not finding all rules in some files - #1405.When pint finds the exact same problem generating multiple problem reports it will now hide duplicated reports. There is a new flag pint --show-duplic
When pint finds the exact same problem generating multiple problem reports it will now hide duplicated reports.
There is a new flag pint --show-duplicates ... that you can use to show all instances of each problem.
For example if we have three different rules with the same smelly selector:
groups:
- name: foo
rules:
- record: events:a
expr: events_total{instance="a", job=~"foo.+"}
- record: events:b
expr: events_total{instance="b", job=~"foo.+"}
- record: events:c
expr: events_total{instance="c", job=~"foo.+"}
Previous versions of pint would print each problem:
Warning: smelly regexp selector (promql/regexp)
---> rules/1.yaml:5 -> `events:a`
5 | expr: events_total{instance="a", job=~"foo.+"}
^^^^^^^^^^^^ `{job=~"foo.+"}` looks like a smelly selector ...
Warning: smelly regexp selector (promql/regexp)
---> rules/1.yaml:7 -> `events:b`
7 | expr: events_total{instance="b", job=~"foo.+"}
^^^^^^^^^^^^ `{job=~"foo.+"}` looks like a smelly selector ...
Warning: smelly regexp selector (promql/regexp)
---> rules/1.yaml:9 -> `events:c`
9 | expr: events_total{instance="c", job=~"foo.+"}
^^^^^^^^^^^^ `{job=~"foo.+"}` looks like a smelly selector ...
This release of pint will (by default) show it only once:
Warning: smelly regexp selector (promql/regexp)
---> rules/1.yaml:5 -> `events:a` [+2 duplicates]
5 | expr: events_total{instance="a", job=~"foo.+"}
^^^^^^^^^^^^ `{job=~"foo.+"}` looks like a smelly selector ...
pint_problem metrics exposed when running pint watch were lacking problem details.
pint_problem metrics exposed when running pint watch were lacking problem details.Labels set on the group level are now supported by pint.
snooze comments with a metric selector.Don't try to report problems to BitBucket for unmodified rules.
Fixed a panic when parsing empty documents - #1355.
promql/series check will now output more accurate comments.
alerts/template check will now output more accurate comments.
Fix promql/series to not fail on absent({...}) calls.
absent({...}) calls.Some parts of comments reported to GitHub & GitLab were not using collapsible blocks as intended.
Print only relevant lines when reporting problems.
Don't create empty markdown blocks when reporting problems to GitHub & GitLab.
Added names option to the parser block, which controls how does Prometheus validates label names.
names option to the parser block, which controls how does Prometheus validates
label names.ignoreMatchingElsewhere option to promql/series check.bug to a warning.foo unless bar will now only have foo
tested while bar is ignored by this check. This is because the query implies that bar
might be present or missing and depending on that foo is evaluated.{code=~"5.*"}) as smelly in promql/regexp check.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
When running pint watch command /health HTTP endpoint can now be used for liveness probes.
pint watch command /health HTTP endpoint can now be used for liveness probes.When pint runs online checks against Thanos or other service that implements some, but not all, Prometheus APIs
it would reports errors due to some API requests returning 404 Not Found HTTP errors.
Now pint will automatically disable checks that rely on Prometheus API endpoints that are not supported
and create a summary comment (when running pint ci) that lists disabled checks.
This applies to these API endpoints:
/api/v1/status/config/api/v1/status/flags/api/v1/metadataNothing published for this version
### Fixed - # pint file/owner comments were not validated properly for files with no rules. This is now fixed.
# pint file/owner comments were not validated properly for files with no rules.
This is now fixed.Added schema option to the parser configuration block for setting rule validation schema. This option is only used when files are parsed in strict mod
Added schema option to the parser configuration block for setting rule validation
schema. This option is only used when files are parsed in strict mode - which is when
rule file path does NOT match any of the parser:relaxed regex values or when simply
parser:relaxed is not set at all.
Default value is prometheus and tells pint to expect rule files with the schema
expected by Prometheus itself. If you use pint to validate rules loaded into Thanos Rule
component then set schema to thanos in your pint config file:
parser {
schema = "thanos"
}
File schema when using schema: prometheus (default):
groups:
- name: example
rules:
- record: ...
expr: ...
- alert: ...
expr: ...
When using schema: thanos:
groups:
- name: example
partial_response_strategy: abort
rules:
- record: ...
expr: ...
- alert: ...
expr: ...
Rules configured in pint config can now be locked - when a rule is locked it cannot
be disabled by users by adding a # pint disable ... or # pint snooze ... comments.
--no-color flag is set.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
pint now uses Prometheus 3.0 libraries for parsing PromQL, which adds support for new query syntax that allows for dots and UTF-8 chars in metric/labe
pint now uses Prometheus 3.0 libraries for parsing PromQL, which adds support for new query syntax that allows for dots and UTF-8 chars in metric/label names, example:
{"status.üp"} == 0
promql/rate will now report a warning if it detects a rate(sum(...))
but doesn't have metadata to confirm if ... is a counter or not.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fixed a crash when parsing vector() calls with non-number arguments.
vector() calls with non-number arguments.Nothing published for this version
Improved the accuracy of alerts/template check.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Improved message formatting in the alerts/template check.
Your coding agent can read these notes before it upgrades. Set up the MCP server →