NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #1789 by repository stars
Last release 2 days ago
06 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
402 releases · first in 2021
One column per quarter.
Improved message formatting in the alerts/template check.
Nothing published for this version
Nothing published for this version
Added --checkstyle flag to pint lint & pint ci for writing XML report file in checkstyle format - #1129.
Added --checkstyle flag to pint lint & pint ci for writing XML report file
in checkstyle format - #1129.
Added --json flag to both pint lint and pint ci commands, this enables writing a JSON file
with the report of all problems #606.
promql/fragile will now warn when alerting rules are using one of the aggregation operation that can return different series on every evaluation, which can cause alert floppiness - #820.
promql/regexp check now supports extra configuration options to disable reports on smelly selector - #1096.
Checks can be enabled or disabled specifically for some Prometheus rules via rule {} config blocks.
Adding enable or disable option with a list of checks names allows to selectively enable or disable
checks only for Prometheus rules that match given rule {} definition.
Enabling checks only for matching rules will only work if these checks are disabled globally via
check { disabled = [] } config block.
For example to disable promql/rate check for all rules except alerting rules in the rules/critical folder:
checks {
// This will disable promql/rate by default.
disabled = [ "promql/rate" ]
}
rule {
match {
path = "rules/critical/.*"
kind = "alerting"
}
// This will enable promql/rate only for Prometheus rules matching all our match conditions above.
enable = [ "promql/rate" ]
}
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fixed message formatting in the promql/series check.
Nothing published for this version
Added fallbackTimeout option to the promql/series check that controls how much time pint can spend checking other Prometheus servers for missing metri
fallbackTimeout option to the promql/series check
that controls how much time pint can spend checking other Prometheus servers for missing
metrics.Fixed colored output on some environments - #1106 change
as it was breaking GitHub report comments.Nothing published for this version
Nothing published for this version
Fixed GitHub actions permissions.
Nothing published for this version
Improved accuracy of the rule/duplicate 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
Fixed a bug in match block state handling that caused all rules to always match any state.
match block state handling that caused all rules to always match any state.promql/regexp check will now look for smelly regexp selectors. See check docs for details.
--enabled flag to the pint command. Passing this flag will only run selected check(s).state option to the rule match block. See configuration docs for details.parser block exclude list.
This is to avoid trying to parse it as a rule file if it's included in the same folder as rules.Nothing published for this version
Added ignoreLabelsValue to promql/series check settings.
ignoreLabelsValue to promql/series check settings.include & exclude options were moved from the ci to the parser configuration block.
They now apply to all pint commands, not just pint ci - #631.promql/vector_matching will now report more details, including which Prometheus server reports problems and which part of the query is the issue.
pint ci pint will now run all checks on unmodified rules when a file/disable comment was removed.absent_over_time().When using BitBucket reporter pint ci might create a comment longer than the limit allowed by BitBucket. To avoid this pint will now truncate long com
pint ci might create a comment longer than the limit allowed by BitBucket.
To avoid this pint will now truncate long comments.Nothing published for this version
Fixed false positive warnings from rule/dependency check.
promql/series check will now generate warnings if there are # pint disable or # pint rule/set comments that are not matching any valid query selector
# pint disable
or # pint rule/set comments that are not matching any valid query selector or Prometheus server.rule/set comments that target specific
time series selectors in PromQL the same way as # pint disable comments do.Fixed false positive reports about removed rules when running pint ci on a branch that contains YAML syntax errors.
pint ci on a branch that
contains YAML syntax errors.Nothing published for this version
Fixed release workflow on GitHub.
Don't suggest using humanize when alert template is already using printf on format the $value.
humanize when alert template is already using printf on format the $value.pint ci on a branch that include merge commits.Nothing published for this version
alerts/annotations and rule/label will now report when a label or annotation is required but set to an empty value.
# pint ignore/line comments on line including multiple # characters.publicURI from each prometheus definition.Added GitLab support when running pint ci.
pint ci.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Correctly handle default Prometheus retention value in promql/range_query check - #958.
Nothing published for this version
Fixed false positives from rule/duplicate check when running pint ci on files that are both edited and renamed in the same PR.
pint ci on files that are both edited and renamed in the same PR.Nothing published for this version
Fixed compatibility with older git releases.
maxComments defaulting to zero when using GitHub reporter.maxComments comment creation on GitHub - #935.Nothing published for this version
Fixed release workflow on GitHub actions.
Nothing published for this version
Nothing published for this version
GitHub and BitBucket reporters now supports maxComments option to limit the number of comments pint can create on a single pull request. Default value
maxComments option to limit the number
of comments pint can create on a single pull request.
Default value of maxComments is 50.Nothing published for this version
query/cost will now only create reports if a query is more expensive than any of the configured limits.
promql/counter check will now consider a metric to be a counter only if all metadata entries for it use TYPE counter. Previously it would check for at
TYPE counter.
Previously it would check for at least one metadata entry with TYPE counter.Nothing published for this version
Added promql/counter check - #655.
Added promql/counter check - #655.
Check using custom rules now accept an optional comment option for adding
a text comment to all reported problems.
Checks supporting comment option:
for {
comment = "All alert rules must have `for: 5m` (or more) to avoid flaky alerts."
severity = "bug"
min = "5m"
}
Nothing published for this version
Nothing published for this version
Nothing published for this version
labels/conflict check will now warn if alerting rule is setting labels that are already configured as external labels.
pint watch command now has two sub-commands: pint watch glob and pint watch rule_files.
See watch mode docs for details.
promql/series check will now ignore missing metrics if the
query uses a fallback with or vector(1). This will reduce the number of reported
missing metrics for queries where the intention is to accept and ignore missing
metrics.
Example of a rule that will no longer report problems:
- alert: Foo
expr: sum(my_metric or vector(0)) > 1
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →