NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1810 by repository stars
Latest stable
v0.90.0
Last release 11 days ago
11 Nov 2026
Ships on a steady schedule
a new release about every 1 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
420 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
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.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
8474620b28d5cc8c8fe19c8404b7a1d826aa48db: More strict type checks for promql/counter (@prymitive)
TYPE counter.
Previously it would check for at least one metadata entry with TYPE counter.Nothing published for this version
9c2ce7315ea76cb5c45f43076d87489775c264d9: Add comment option to all checks (@prymitive)
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
9dbc0c2ee85133df89541f1c42beec80070cf9de: Add more checks to labels/conflict (@prymitive)
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
Nothing published for this version
Nothing published for this version
b18025cab5fe7e6efe767253c8252098639cd2c0: Add missing tools (@prymitive)
rule/dependency check will now warn if an alerting rule
that's being removed in a pull request is being used inside ALERTS{alertname="..."}
or ALERTS_FOR_STATE{alertname="..."} queries.
pint will now perform extra validation of YAML files to ensure that all values are mappings and strings. This will error on rules where, for example, label value is unquoted number:
Bad rule:
- alert: DeadMansSwitch
expr: vector(1)
labels:
priority: 5
Good rule:
- alert: DeadMansSwitch
expr: vector(1)
labels:
priority: "5"
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
Nothing published for this version
Nothing published for this version
37449a17ad3f09103053b2705b0d8a0cda4704de: Bump github.com/rogpeppe/go-internal from 1.11.0 to 1.12.0 (@dependabot[bot])
pint ci and using ignore/file comments.Nothing published for this version
Nothing published for this version
a3e47a812bf237e9378d0c57f437e0960552109d: Add more tests (@prymitive)
token option.
In addition to the value regexp matching you can also validate values against a static
list of allowed values using new values option.
See both checks documentation for detail.5afe923e76305d28a0662ce24a2ebfa1c8bd099b: Bump actions/setup-go from 4 to 5 (@dependabot[bot])
d11fcb0279d766b8b1a4d1944fd29e518b8b948c: Add more test rules (@prymitive)
pint ci pint will now first try to parse all files in current
working directory, before checking for files modified on current branch.
This is to have a full list of all rules, which is needed for checks like
newly added rule/dependency.
This can slow pint runs if there's a lot of files in your repository.
If there are non-rule files these may fail to parse and result in check errors.
To avoid any errors or slowdowns from scanning unrelated files you might need
to add ci section to .pint.hcl with include and/or exclude options set.
See examples/ci.hcl for an example config.Bug and Fatal severity problems are now reported as tasks when using
BitBucket.pint will no longer run dynamic Prometheus discovery when --offline flag
is passed.8e1fe24182de1af6dbbd944a72e1976550e10e98: Bump debian from stable-20231030 to stable-20231120 (@dependabot[bot])
pint ci now uses a new logic for deciding which rules have changed when validating
pull requests. Changes that would previously be invisible to pint, like modifying
comments or moving the entire rules file, will now trigger checks for affected
rules.Control comments section in pint docs.2ec51e2dfb93496c06e61538a1f9cf94f14a7f4d: Bump github.com/gkampitakis/go-snaps from 0.4.11 to 0.4.12 (@dependabot[bot])
promql/regexp - #782.Information level reports using BitBucket were using wrong comment icon.Nothing published for this version
15a0d03371acf6a1a3391d620ed99e76d24a92b5: Fix alerts/count gap detection (@prymitive)
alerts/count check wasn't using uptime field from prometheus config blocks
for metric gap detection.Nothing published for this version
2365f73d2de25201377996d7850bb49e1e591545: Add more details to problem reports (@prymitive)
pint --teamcity lint or pint --teamcity ci.publicURI field to prometheus configuration blocks.Nothing published for this version
c78a1955fa87e1bac9faeefb31e3d6da328b8843: Fixed watch mode (@prymitive)
pint watch to correctly work with discovery.Nothing published for this version
6b716d129cf970efc0a5d8f8ecaf3fbdee1d5990: Template include & exclude (@prymitive)
template under discovery block can now template
include and exclude fields.Nothing published for this version
fe0554cc86e35806c504fa65536d2da43a04453a: Bump actions/jekyll-build-pages from 1.0.8 to 1.0.9 (@dependabot[bot])
2aa81cc677a5d82b852b80c06eef4ff5ef0dff31: A few slog tweaks (@prymitive)
alerts/template check can now report problems with alerting rules
when trying to use templates on a query that doesn't produce any labels
at all.
For example when using vector(...) function:
{% raw %}
- alert: DeadMansSwitch
expr: vector(1)
annotations:
summary: Deadman's switch on {{ $labels.instance }} is firing
{% endraw %}
alerts/comparison check can now warn if alerting rules use a query
with foo > 0 OR vector(1), which would always fire.
alerts/template check will now look check on(...) clause on binary
expressions. When on(...) is set only labels listed there will appear
on result metrics.
For example app_type here cannot appear on query results, even if it's
present on foo time series.
- alert: ...
expr: foo / on (instance, app_name) bar
annotations:
summary: ... {{ $labels.app_type }} ...
Nothing published for this version
Nothing published for this version
Nothing published for this version
c2ba53d1a03eb57176df976d101c3dc189bd347a: Account for keep_firing_for in Alerts check (@felipesere)
keep_firing_for in the parser (@felipesere)keep_firing_for in alerting rules - #713.rule/keep_firing_for check - #713.alerts/count check will now estimate alerts using
keep_firing_for field if set - #713.match block supports a new filter keep_firing_for.ae3159ae37fc557462961582166cdcbece50a75f: Bump golang from 1.20.6-alpine to 1.20.7-alpine (@dependabot[bot])
query/cost check can now use Prometheus query stats to verify query
evaluation time and the number of samples used by a query. See
query/cost docs for details.Nothing published for this version
Nothing published for this version
4ad9002816304b274cf661c2bb0b49306ad9ae30: Bump actions/jekyll-build-pages from 1.0.7 to 1.0.8 (@dependabot[bot])
promql/series check when Prometheus instance becomes
unavailable - #682.alerts/template check - #681.Nothing published for this version
4b4ce46456c264107b68acb88cd70bec03abdc20: Correctly check for empty names (@prymitive)
Nothing published for this version
71945eb54d5bfb261e9c4a61850b25b2e4ce84ce: Add exclude option to ci block (@prymitive)
exclude option to ci config block - #609.minCount & severity to alerts/count check - #612.
This allows to only show estimated alerts count only if there would be high
enough (>= minCount) number of alerts.
Setting severity as well allows to block rules that would create too many alerts.alerts/annotation check regexp matching - #613.pint ci using GitHub integration annotation comments are now
reported only on modified lines - #640.cb1bc1938d78a1073027f5335b385b727c4c5c17: Fix --base-branch handling (@prymitive)
--base-branch flag handling when branch name contains /.52f9407aed33a9c437b9c8d130866ad10dc4c3fe: Add --fail-on flag to lint command (@prymitive)
--fail-on flag to pint lint command - #570.tls section to prometheus configuration block - #540.{__name__=~"...", foo="bar"} selectors pint could end up
running queries matching a single label, like count({foo="bar"}), which could return too many
results. This version ensures that queries always include name matcher to avoid that.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
f40a538592adf2799da72b50e7ee21c54d960757: Bump github.com/fatih/color from 1.14.1 to 1.15.0 (@dependabot[bot])
alerts/template check didn't correctly handle label_replace() calls
in queries - #568.One column per quarter.