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.
4d3a3e0b99752206add97b831f2cffc2a83ac773: Bump github.com/golangci/golangci-lint in /tools/golangci-lint (@dependabot[bot])
Parsing files in relaxed mode will now try to find rules inside multi-line strings #252. This allows direct linting of k8s manifests like the one below:
---
kind: ConfigMap
apiVersion: v1
metadata:
name: example-app-alerts
labels:
app: example-app
data:
alerts: |
groups:
- name: example-app-alerts
rules:
- alert: Example_Is_Down
expr: kube_deployment_status_replicas_available{namespace="example-app"} < 1
for: 5m
labels:
priority: "2"
environment: production
annotations:
summary: "No replicas for Example have been running for 5 minutes"
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
9de1a3d2783ec8af68d59d538a03a965d24a7990: Add alert example (@prymitive)
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
e7565889334554035e731a1241af2c60cc0b1473: Bump github.com/hashicorp/hcl/v2 from 2.11.1 to 2.12.0 (@dependabot[bot])
promql/series check with extra control comments
# pint rule/set promql/series min-age ... and
# pint rule/set promql/series ignore/label-value ...
See promql/series for details.promql/regexp will report redundant use of regex anchors.promql/series will now report missing metrics only if they were last seen
over 2 hours ago by default. This can be customised per rule with comments.352137df9d2e28c178a8ffc3e7890eee1ebbb6ee: Fix rule/owner line reporting (@prymitive)
rule/owner check.rule/owner documentation page.8ae5836537b055576195414176ef736111a685bb: Correctly set timestamps in promql/series (@prymitive)
promql/series check when running
pint watch.c3fd53fc0eb6ff31554139f7f5748d6c3e7d51a5: Add require owner flag to ci command (@prymitive)
pint_last_run_duration_seconds metric.--require-owner flag support to pint ci command.f97b24cb38b8902d97d10dffae4cb2838fd0dbfd: Fix absent checks (@prymitive)
alerts/template check when absent() is
used inside a binary expression.db62066ce1f51fd9317d4ffabdf20f06057b8d36: Correctly report line numbers (@prymitive)
pint ci.6f0aa8a55414ca4f553d48ffbe3070455ba0b3de: Correctly report file parse errors in CI (@prymitive)
pint ci.852d2bd2e60fb48d5ef5a3398f69f116fa25f73c: Correctly handle 504s (@prymitive)
504 Gateway Timeout HTTP responses from Prometheus same as query
timeouts and retry with a shorter range query.b52bd8e46c8dd80fc671fbf505d3ce27094693ba: Enable strict mode by default (@prymitive)
pint ci all checks will be skipped if any commit contains
[skip ci] or [no ci] string in the commit message.By default pint will now parse all files in strict mode, where all rule files must have the exact syntax Prometheus expects:
groups:
- name: example
rules:
- record: ...
expr: ...
Previous releases were only looking for individual rules so groups object
wasn't required. Now pint will fail to read any file that doesn't follow
Prometheus syntax exactly.
To enable old behaviour add parser { relaxed = ["(.+)", ...]} option in
the config file. See Configuration for details.
To enable old (relaxed) behaviour for all files add:
parser {
relaxed = ["(.*)"]
}
promql/vector_matching checks to detect more issues.pint ci.f08676c2fdb69a0f0ee35e5076597f469d95bed4: Make absent() checks aware of binary expressions (@prymitive)
alerts/template check when absent() function
is receiving labels from a binary expression.4ce0bf5fb37e303adf238c2bf8efa15bd7c062cc: Allow setting rule owner via comments (@prymitive)
pint watch exported metric can include owner label for each rule.
This is useful to route alerts based on pint_problem metrics to the right team.
To set a rule owner add a # pint file/owner $owner comment in a file, to set
an owner for all rules in that file. You can also set an owner per rule, by adding
# pint rule/owner $owner comment around given rule.
To enforce ownership comments in all files pass --require-owner flag to pint lint.Nothing published for this version
ced4e688d8b7e815166ee5ba7cfb81737407bce4: Bump github.com/golangci/golangci-lint in /tools/golangci-lint (@dependabot[bot])
promql/series check no longer runs duplicated checks on source metrics when
a query depends on a recording rule added in the same PR.bfe00558a3cc63506083dc0c8fa34f119e0ba9d9: Correctly check for sample time ranges (@prymitive)
promql/series check was reporting that a metric stopped being exported when check
queries would require a few retries.e423faafd3cb6097c497d0cc85bfdc2423a74b2a: Bump actions/cache from 2 to 3 (@dependabot[bot])
promql/series check was reporting both Warning and Bug problems for the
same metric when it was using newly added recording rule.Nothing published for this version
71d5eb33223393b00915b5583229737a12eccfed: Add more test coverage (@prymitive)
promql/fragile when foo OR bar is used inside
aggregation.7d1ea938f5cb592aec3f7b754f4e75b51bce01ed: Add fuzz tests to CI (@prymitive)
promql/series check.0483c1c08995939804a6c8bbcc86f617ef265b46: Improve cache hit rate (@prymitive)
pint_prometheus_cache_hits_total metric
to track the number of cache hits.79fa0cd3b8ac61a19569a920bcf01775e0b6f1ed: Speed up expensive queries in watch mode (@prymitive)
query processing would load too many samples into memory
error and we retry it with smaller time range cache this information and start with
that smaller time range for future calls to speed up running pint watch.c7172b768ccff2396ec4d9efb2cb0392ac3ae69f: Always print the number of detected problems (@prymitive)
pint lint.promql/series check was refactored and will now detect a range of
problems. See promql/series for details.promql/regexp severity is now Bug instead of a Warning.promql/rate check will no longer produce warnings, it will only
report issues that cause queries to never return anything.5ec11c17ff040cb518b93a692e2a4aebd0e2b7e2: Add filename label to pint_problem metric (@prymitive)
Allow matching alerting rules by for field - #148. Example:
rule {
match {
for = ">= 10m"
}
}
Regexp matchers used in check rules can now reference rule fields. See Configuration for details.
filename label to pint_problem metric - #170.pint ci handling when a file was added to git and then removed in the
next commit.Nothing published for this version
d0bf6791ff78b9a8b1c1b004b0e6217f614e7c28: Don't failover in case of query errors (@prymitive)
many-to-many matching not allowed.7778dd95ff9c710a2061b92bb7d28501bce70544: Enable more codeql checks (@prymitive)
yaml/parse error will be raised if a rule file contains duplicated keys, example:
- record: foo
expr: sum(my_metric)
expr: sum(my_metric) without(instance)
prometheus config block now allows to specify fail-over URIs using failover field.
If fail-over URIs are set and main URI fails to respond pint will attempt to use them
in the order specified until one of them works.prometheus config block now allows to define how upstream errors are handled using
required field. If required is set to true any check that depends on remote
Prometheus server will be reported as bug if it's unable to talk to it.
If required is set to false pint will only emit warning level results.
Default value for required is false. Set it to true if you want to hard fail
in case of remote Prometheus issues. Note that setting it to true might block
PRs when running pint ci until pint is able to talk to Prometheus again.pint/parse to yaml/parse and added missing documentation for it.16fcd89404d65490a32bb09542be2ba014d53efa: Add pint_last_run_time_seconds metric (@prymitive)
pint_last_run_time_seconds and pint_rules_parsed_total metrics when running pint watch.promql/comparison only applies to alerts, so it was renamed to
alerts/comparison.alerts/count check will now retry range queries with shorter time window
on found duplicate series for the match group ... errors from Prometheus.772ca6a530385c3bcac79a4239f9a81420edef63: Fix promapi metric usage (@prymitive)
pint_prometheus_queries_total and pint_prometheus_query_errors_total metrics
were not incremented correctly.a10c5b43bb63e8d1c9600ad3ed64dd1fdc1195b5: Add pint_prometheus_query_errors_total metric (@prymitive)
promql/regexp check that will warn about unnecessary regexp matchers.pint_prometheus_queries_total and pint_prometheus_query_errors_total
metric when running pint watch.bb2d6a2ec2a8bc0ca2b6e08cfd749e64fadd6d5c: Improve promql/vector_matching check query rewrites (@prymitive)
promql/vector_matching check.173eb627e34e9407dbe35ccf609b97f7d2b8676d: Improved the logic of check (@prymitive)
query/series check was renamed to promql/series.promql/vector_matching check.497633946182d4c49e75bfc218ac8ca08d718bfa: Allow multiple match/ignore blocks per rule (@prymitive)
lines label from pint_problem metric exported when running pint watch.match and ignore blocks can now be specified per each rule.4ccd988ff00c9c1da11f01d319fb64bd053ceff5: Add --min-severity flag (@prymitive)
pint_version metric when running pint watch.--min-severity flag to pint watch command.637daedbf900fc7cc803a9ecb6e85c8e7b20e93f: Add --max-problems flag to pint watch (@prymitive)
--max-problems flag to pint watch command.stripPort template function.61198e795a5069f929901e79b6534239ab76d63b: Add a link to BB reports (@prymitive)
promql/fragile check.f2481e906342657ef909f5f50674262b3d9ebded: Add --workers flag (@prymitive)
--workers flag to control the number of worker threads for running checks.More aggressive range reduction for query processing would load too many samples into memory errors when sending range queries to Prometheus servers.
query processing would load too many samples into memory
errors when sending range queries to Prometheus servers.58e70024236ec9b1527d94c16fb8c7cd62ca0478: Add command filter to match/ignore (@prymitive)
command filter to match / ignore blocks. This allows to include
skip some checks when (for example) running pint watch but include them
in pint lint run.3104d3fb6a41e8e7ab1a5a862900eb112fd73bef: Add more test coverage (@prymitive)
pint watch will start a daemon that will continuously check all matching rules
and expose metrics describing all discovered problems.alerts/annotation and rule/label now include required flag value in
# pint disable ... comments.
Rename # pint disable alerts/annotation($name) to
# pint disable alerts/annotation($name:$required) and
# pint disable rule/label($name) to # pint disable rule/label($name:$required).--offline and --disabled flags are now global, use pint --offline lint instead
of pint lint --offline.promql/rate, query/series and promql/vector_matching checks were not enabled
for all defined prometheus {} blocks unless there was at least one rule {} block.annotation based match blocks didn't work correctly.Nothing published for this version
a6cd31096ca3dc840b1ae5649ac0a1609c152889: Fix file rename handling in git (@prymitive)
git ci on branches with
multiple commits.080b29fd05b68ec823befc8658a08583ca23c28d: Allow disabling individual query/series checks (@prymitive)
query/series check for individual series using
# pint disable query/series(my_metric_name) comments.a5c7617873dc404913e10ab1d20eebca1795da4d: Fix docker builds (@prymitive)
aggregate check didn't report stripping required labels on queries using aggregation with no grouping labels (sum(foo)).
aggregate check didn't report stripping required labels on queries
using aggregation with no grouping labels (sum(foo)).aggregate check didn't test for name and label matches on alert rules.f175acbf7341a8e7ffe4a9d8e751ee72ce9724df: Include query lines in template check errors (@prymitive)
template check will now include alert query line numbers when reporting issues.bedea1ee049606a4a25b6394932ea3c7e5591f33: Fix absent() checks (@prymitive)
absent() are only from equal match types (absent(foo="bar"),
not absent(foo=~"bar.+") but alerts/template didn't test for match type when
checking for labels sourced from absent() queries.f47d58ba472e4e3aebe9aa29d473d4bf72e3c568: Add more test coverage (@prymitive)
aggregate check was refactored and uses to run a single test for both
by and without conditions. As a result this check might now find issues
previously undetected.
Check suppression comments will need to be migrated:
# pint disable promql/by becomes # pint disable promql/aggregate# pint disable promql/without becomes # pint disable promql/aggregate# pint ignore promql/by becomes # pint ignore promql/aggregate# pint ignore promql/without becomes # pint ignore promql/aggregatecbb4e9bd0f739d539a2b384a28f5d54ded6eb0cc: Don't enable multiple instances of the same check (@prymitive)
--no-color flag for disabling output colouring.rule {...} blocks where configured.c63478b018ae094fa139636f9dcbd662596ae449: Bump github.com/rogpeppe/go-internal from 1.8.0 to 1.8.1 (@dependabot[bot])
# pint disable ... comments on a single rule would only apply
last comment. This now works correctly and all comments will be applied.Nothing published for this version
60bd0db71419e107a46455d83e3921e84ba28ca2: Simplify configuration (@prymitive)
alerts/for check that will look for invalid for values in alerting rules.
This check is enabled by default.comparison check is now enabled by default and require no configuration.
Remove comparison{ ... } blocks from pint config file when upgrading.template check is now enabled by default and require no configuration.
Remove template{ ... } blocks from pint config file when upgrading.rate check is now enabled by default for all configured Prometheus servers.
Remove rate{ ... } blocks from pint config file when upgrading.series check is now enabled by default for all configured Prometheus servers.
Remove series{ ... } blocks from pint config file when upgrading.vector_matching check is now enabled by default for all configured Prometheus servers.
Remove vector_matching{ ... } blocks from pint config file when upgrading.b5ca45b80bb2db4dae4dca7ec4fb168644c4662a: Support Prometheus 2.32.0 (@prymitive)
parseDuration function in alert templates added in Prometheus 2.32.0One column per quarter.