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.
Nothing published for this version
e213189c05bfa238a54b57e483adf7e20e151070: Correctly pass base branch flag (@prymitive)
--base-branch flag handling.
Value of this flag wasn't being used correctly - #559.e18612059a73198b6b6d86493f75388c0c20f51d: Bump debian from stable-20230208 to stable-20230227 (@dependabot[bot])
Your coding agent can read these notes before it upgrades. Set up the MCP server →
promql/series check for time series with only a single
data point.d901f9439d6e00ff4b713c7265740aff80b2498c: Bump github module to v50 (@prymitive)
for field values with long durations (for: 1d).Nothing published for this version
bc6480523702c489114fa8b3cf265cbb8794c8a4: Add pint ci --fail-on flag (@prymitive)
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
7f47f1ef65d209dd2009d6475bab393b96be0164: Avoid incorrect label errors when a series disappears (@prymitive)
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.877d0ca14724f9fa6d9dea4a8bf623b2d587cf04: Add extra options to promql/series check (@prymitive)
# pint file/snooze ... comments.lookbackRange and lookbackStep configuration option to the
promql/series check - #493.Nothing published for this version
a1e0c745079a6a3404ea0605d53e5ff8daa54173: Use checks run API for github integration (@prymitive)
1f974dc1a2eec2bda9b010e629dfc3da3d868731: Fix tags support in file/disable comments (@prymitive)
# pint file/disable comments didn't properly handle Prometheus tags, this is fixed now.f82c4c050fcb24ff0767296d1d510095a8542f9c: Add more tests (@prymitive)
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.c61328be05bf66af24b29438b907ae13467d26f0: Added pint_rule_file_owner metric (@prymitive)
Nothing published for this version
083787e767f8098f637db5edcefdb35ebb5a4a7a: Add more env variable tests (@prymitive)
Nothing published for this version
Nothing published for this version
0c66d411208e889a2c360b8b022186978ae49004: Add labels/conflict check (@prymitive)
Use uber-go/automaxprocs to automatically set GOMAXPROCS to match Linux container CPU quota.
Added labels/conflict check.
If you want to disable individual checks just for some time then you can now snooze them instead of disabling forever.
The difference between # pint disable ... and # pint snooze ... comments is that
the snooze comment must include a timestamp. Selected check will be disabled until
that timestamp.
Timestamp must either use RFC3339 syntax
or YYYY-MM-DD (if you don't care about time and want to snooze until given date).
Examples:
# pint snooze 2023-01-12T10:00:00Z promql/series
# pint snooze 2023-01-12 promql/rate
- record: ...
expr: ...
Removed cache option from prometheus config blocks. Query cache will now auto-size itself
as needed.
If you have a config entry with cache option, example:
prometheus "prod" {
uri = "https://prometheus.example.com"
cache = 20000
}
Then pint will fail to start. To fix this simply remove the cache option:
prometheus "prod" {
uri = "https://prometheus.example.com"
}
15384f12385374a1bf6dc7a2c8c62e204e8827d2: Add more test coverage (@prymitive)
f3f8cdad1a5508c711c8cfe9f20bb51e48ce684f: Fix query cache hit rate (@prymitive)
47b525d36a0fb556193e3710567f0f4b2293ee17: Bump actions/dependency-review-action from 2 to 3 (@dependabot[bot])
Added uptime field in prometheus configuration block.
This field can be used to set a custom metric used for Prometheus uptime checks
and by default uses up metric.
If you have a Prometheus with a large number of scrape targets there might
be a huge number of up time series making those uptime checks slow to run.
If your Prometheus is configured to scrape itself, then you most likely want to use
one of metrics exported by Prometheus, like prometheus_build_info:
prometheus "prod" {
uri = "https://prometheus.example.com"
uptime = "prometheus_build_info"
}
cache option for prometheus config block now means
the number of time series cached instead of the number of responses cached
and the default for this option is now 50000.a9b94b4dd9f1358039514512e4335b6ddf41a6e9: Never send raw queries from promql/vector_matching (@prymitive)
6b1c58c3b100d918bc32f862f05e3b8fca01c347: Add more tests (@prymitive)
pint_prometheus_cache_evictions_total metric tracking the number of times
cache results were evicted from query cache.# pint file/disable ... comments.prometheus block names.Nothing published for this version
61ce0392558683ddd0fd8ac86f2a2a490ecf0323: Bump github.com/gkampitakis/go-snaps from 0.4.0 to 0.4.1 (@dependabot[bot])
pint watch over time.82cac8bc3941273593d08e5da947d79f428d1bf2: Allow setting request headers for Prometheus (@prymitive)
prometheus configuration block now accepts optional headers field, for setting
request headers that will be attached to any request made to given Prometheus server.
Example:
prometheus "protected" {
uri = "https://prod.example.com"
headers = {
"X-Auth": "secret",
"X-User": "bob"
}
Fixed false positive reports in promql/vector_matching
for rules using on(...). Example:
sum(foo) without(instance) * on(app_name) group_left() bar
Don't log passwords when Prometheus URI is using basic authentication.
Fixed false positive reports in alerts/template
suggesting to use humanize on queries that already use round().
Fixed false positive reports in alerts/comparison
when bool modifier is used on a condition that is guarded by another condition.
Example:
alert: Foo
expr: (foo > 1) > bool 1
Fixed false positive reports in alerts/template warning about labels removed in a query despite being re-added by a join.
3f648de4182904fcc503ecc10f1bc08c5da38324: Fix wrong line numbers on annotations (@prymitive)
f8bb17b3491fada3fe70b8b991806b8785c92b35: Fix lint handling of symlinks (@prymitive)
pint lint and pint watch commands.b5ee8ee35ebca16edfda6d8689e9c0d473bf81da: Add codecov config (@prymitive)
BitBucket only allows for annotations on modified lines, so when a high severity problem is reported on unmodified line pint will move that annotation to the first modified line, so it's still visible in BitBucket. Now pint will also add a note to that annotation to make it clear that the problem is really on a different line.
alerts/template will now run extra checks to validate syntax of queries executed from within alerting rule templates.
Example template using sum(xxx query that's missing closing ):
{% raw %}
- alert: ...
expr: ...
annotations:
summary: |
{{ with query "sum(xxx" }}
{{ . | first | value | humanize }}
{{ end }}
{% endraw %}
If a file is ignored pint will now note that using Information level annotation.
This will make it more obvious that a CI check passed because pint didn't run any
checks due to file being excluded.
Prometheus rule files can be symlinked between directories. If the symlink source and target files are in a different directory they can end up querying different Prometheus server when running ping checks. This means that when modifying symlink target file checks must be executed against both symlink source and target. Until now pint was ignoring symlinks but starting with this release it will try to follow them. This means that if you modify a file that has symlinks pointing to them pint will try run checks against those symlinks too.
NOTE: pint can only detect and check symlinks if they are located in the current working directory (as seen by running pint process) or its sub-directories.
b851aaad710292682cf3994b3ca9991b974d0aec: Bump github.com/gkampitakis/go-snaps from 0.3.6 to 0.3.7 (@dependabot[bot])
1ae7e5a71dbd3b15bb3644148dbffe3718711411: Bump debian from stable-20220801 to stable-20220822 (@dependabot[bot])
Nothing published for this version
6e7a98ddb0405e7044354ffd074e17ef4cfcb34f: Avoid over-allocating query respones (@prymitive)
e9d2934194f0946a8269fccff9c76b767ca188e4: Fix metadata queries (@prymitive)
ce9831082125bf437160c32022e5fca60975a380: Avoid dupliated results (@prymitive)
promql/rate and promql/regexp checks.48d19c5744acf854bcff557952ce4f46b305d855: Bump github.com/urfave/cli/v2 from 2.11.1 to 2.11.2 (@dependabot[bot])
toTime template function.4d5d3cd2a14c661bc2bfc6201b0cc5823f317a93: Bump debian from stable-20220711 to stable-20220801 (@dependabot[bot])
80eac1c8b888ff67589f164c0e94cab9a03ef5fd: Remove debug logs (@prymitive)
6b7c56876c3dc6f24ce61b2e36fcbaffdeeac5c1: Purge expired cache on interval (@prymitive)
pint_prometheus_cache_miss_total metric.File parsed messages.241c1537da73c3a4589c866e0c4ba913b4e00eea: Better absent() handling (@prymitive)
4a4bf83f1b449f4472903eaa2fa023d30e53881b: Add --min-severity flag to pint lint (@prymitive)
--min-severity flag to the pint lint command. Default value is set to warning.metric is generated by alerts ....a1ff9d05ff455241b047be798721bdcd192fdb9e: Avoid topk() in vector_matching check (@prymitive)
topk in promql/vector_matching check to
avoid false positives.9422321e8200f5c5f2c1fffc8cf41221372f76c4: Add multiple new changes for v0.28 (@prymitive)
deriv function usage.rate() and the value
is used in annotations.promql/series check now supports more flexible
# pint disable promql/series(...) comments.
Adding a comment # pint disable promql/series({cluster="dev"}) will disable this check
for any metric selector with cluster="dev" matcher.
query/cost check will now calculate how much Prometheus memory
will be needed for storing results of given query.
bytesPerSample option that was previously used to calculate this was removed.
prometheus {} config block now allows to pass a list of paths to explicitly ignore
by setting exclude option. Existing paths option was renamed to include for
consistency. Example migration:
prometheus "foo" {
[...]
paths = [ "rules/.*" ]
}
becomes
prometheus "foo" {
[...]
include = [ "rules/.*" ]
}
pint_last_run_checks and pint_last_run_checks_done were not updated properly.89d6a5a5c9568d987a128eba78c20f955f41c4b5: Add a rule/link check (@prymitive)
pint lint.e98c946ce30f5e57c8ece60d3b02934efea879cd: Add promql/range_query check (@prymitive)
alerts/template check.c90e632ba19be6a3b721774d1840f84270ecbb6c: Better support for github actions (@prymitive)
prometheus { timeout = ... }repository { bitbucket { timeout = ... } }repository { github { timeout = ... } }pint will now try to discover all repository settings from environment variables
when run as part of GitHub Actions workflow and so it doesn't need any
repository { github { ... } } configuration block for that anymore.
Setting GITHUB_AUTH_TOKEN is the only requirement for GitHub Actions now.cfbb2842642b810281fa3045c076a956121aea37: Add more linters (@prymitive)
--base-branch flag to pint ci command.Nothing published for this version
e6b7fdefd88fd093b68e86838f873722dff477c4: Add a rate limit for Prometheus API requests (@prymitive)
rateLimit field inside selected
prometheus server definition.pint_last_run_checks and pint_last_run_checks_done metrics to track
progress when running pint watch.d3253d52c57c327254589f7dbdf0ff20211de587: Add extra settings for promql/series (@prymitive)
promql/series check.
See check documentation for details.prometheus server definition in pint config file can now accept optional
cache field (defaults to 10000) to allow fine tuning of built-in Prometheus
API query caching.pint_prometheus_cache_size metric that exposes the number of entries
currently in the query cache.918cb4c3a24ac549bd16b07f4649a6342cf85d3b: Bump github.com/prometheus/prometheus from 0.36.1 to 0.36.2 (@dependabot[bot])
Nothing published for this version
c73a90ee5a3ce05f65e9e3dffb13297e5f562eb1: Fix memory usage when running range queries (@prymitive)
Nothing published for this version
b1a2f6f17a76855d28feed108ccd64724f60e9f3: Avoid false positives when Prometheus is down (@prymitive)
The way pint sends API requests to Prometheus was changed to improve performance.
First change is that each prometheus server definition in pint config file can
now accept optional concurrency field (defaults to 16) that sets a limit on how
many concurrent requests can that server receive. There is a new metric that
tracks how many queries are currently being run for each Prometheus server -
pint_prometheus_queries_running.
Second change is that range queries will now be split into smaller queries, so
if pint needs to run a range query on one week of metrics, then it will break
this down into multiple queries each for a two hour slot, and then merge all
the results. Previously it would try to run a single query for a whole week
and if that failed it would reduce time range until a query would succeed.
promql/series handling of rules with {__name__=~"foo|bar"} queries.promql/series would occasionally
report metrics as "sometimes present". This check will now try to find time
ranges with no metrics in Prometheus and ignore these when checking if
metrics are present.e990b8aa1d8eaf5916a739f4f4320991155d6222: Ensure counters are updated (@prymitive)
pint_prometheus_queries_total and pint_prometheus_cache_hits_total metric wasn't
always correctly updated.unknown metric types in promql/rate.49b9fe02028738d31dcb14699b89997b6ddd775d: Add type checks to promql/rate (@prymitive)
promql/rate check will now report if rate() or irate() function is being
passed a non-counter metric.f53c2aefa1f79c45c8dd4d711be11c26fde9409c: Bump github.com/urfave/cli/v2 from 2.8.0 to 2.8.1 (@dependabot[bot])
Nothing published for this version
One column per quarter.