NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #1700 by repository stars
Last release 3 days ago
14 Sep 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
394 releases · first in 2021
One column per quarter.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
pint will now report any comment that looks like a pint control comment but cannot be parsed correctly.
pint ci and using ignore/file comments.Nothing published for this version
Nothing published for this version
Both alerts/annotation and rule/label now support more advance validation of label and annotation values with extra token option. In addition to the v
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.Fixed a few bugs in control comment parsing code.
When running pint ci pint will now first try to parse all files in current working directory, before checking for files modified on current branch. Th
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.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,
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.Fixed false positive reports from promql/regexp - #782.
promql/regexp - #782.Information level reports using BitBucket were using wrong comment icon.Nothing published for this version
alerts/count check wasn't using uptime field from prometheus config blocks for metric gap detection.
alerts/count check wasn't using uptime field from prometheus config blocks
for metric gap detection.Nothing published for this version
Added alerts/external_labels check.
pint --teamcity lint or pint --teamcity ci.publicURI field to prometheus configuration blocks.Nothing published for this version
Fixed pint watch to correctly work with discovery.
pint watch to correctly work with discovery.Nothing published for this version
Prometheus template under discovery block can now template include and exclude fields.
template under discovery block can now template
include and exclude fields.Nothing published for this version
Prometheus servers can now be dynamically configured using one of supported discovery mechanism: file paths or Prometheus metrics query.
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
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
Added support for keep_firing_for in alerting rules - #713.
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.The 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
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
Fixed a crash in promql/series check when Prometheus instance becomes unavailable - #682.
promql/series check when Prometheus instance becomes
unavailable - #682.alerts/template check - #681.Nothing published for this version
Rule names were not checked for correctly, allowing for rules with empty names to pass checks.
Nothing published for this version
Added exclude option to ci config block - #609.
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.Fixed --base-branch flag handling when branch name contains /.
--base-branch flag handling when branch name contains /.Added --fail-on flag to pint lint command - #570.
--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
alerts/template check didn't correctly handle label_replace() calls in queries - #568.
alerts/template check didn't correctly handle label_replace() calls
in queries - #568.Nothing published for this version
Fixed --base-branch flag handling. Value of this flag wasn't being used correctly - #559.
--base-branch flag handling.
Value of this flag wasn't being used correctly - #559.Fixed incorrect results in promql/series check for time series with only a single data point.
promql/series check for time series with only a single
data point.Fixed parsing of alert for field values with long durations (for: 1d).
for field values with long durations (for: 1d).Nothing published for this version
Added --fail-on flag to pint ci command - #525.
Added --fail-on flag to pint ci command - #525.
promql/rate will now look for queries that call
rate() on results of sum(counter) via recording rules.
Example:
- record: my:sum
expr: sum(http_requests_total)
- alert: my alert
expr: rate(my:sum[5m])
Added rule/for check.
Added owners configuration block for setting the list of allowed rule owner values.
See configuration for details.
pint lint output will now include severity level as a text label - #524.Nothing published for this version
Fixed a bug in pint ci that would cause a failure if a directory was renamed.
pint ci that would cause a failure if a directory was renamed.promql/series check when a time series
disappears from Prometheus.promql/range_query check.Allow snoozing checks for entire file using # pint file/snooze ... comments.
# pint file/snooze ... comments.lookbackRange and lookbackStep configuration option to the
promql/series check - #493.Nothing published for this version
GitHub integration now uses Check Runs API - #478.
### Fixed - # pint file/disable comments didn't properly handle Prometheus tags, this is fixed now.
# pint file/disable comments didn't properly handle Prometheus tags, this is fixed now.prometheus configuration blocks now accepts tags field with a list of tags. Tags can be used to disable or snooze specific checks on all Prometheus in
prometheus configuration blocks now accepts tags field with a list of tags.
Tags can be used to disable or snooze specific checks on all Prometheus instances
with that tag.
See ignoring for details.Added pint_rule_file_owner metric.
pint_rule_file_owner metric.Nothing published for this version
Added ability to expand environment variables in pint configuration file. See configuration for details.
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →