fix(deps): update module github.com/victoriametrics/victoriametrics to v1.144.0#2217
Merged
vrutkovs merged 2 commits intoMay 27, 2026
Merged
Conversation
vrutkovs
approved these changes
May 27, 2026
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.143.0→v1.144.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
VictoriaMetrics/VictoriaMetrics (github.com/VictoriaMetrics/VictoriaMetrics)
v1.144.0Compare Source
v1.144.0
Released at 2026-05-22
FEATURE: all VictoriaMetrics components: improve logging for the
-memory.allowedBytesflag to warn about excessively low value (less than 1MB). See issue #10935.FEATURE: vmagent and vmalert: add
basicAuth.usernameFilecommand-line flags for reading basic auth username from a file, similar to the existingbasicAuth.passwordFile. The file is re-read every second. See #9436. Thanks to @kimjune01 for the contribution.FEATURE:
vminsertin VictoriaMetrics cluster: addclusternative.tlsvminsertconfiguration flags for multi-level cluster setups. See #10958.FEATURE: vmsingle,
vminsertin VictoriaMetrics cluster and vmagent: add-opentelemetry.labelNameUnderscoreSanitizationcommand-line flag to control whether to enable prepending ofkeyto labels starting with_when-opentelemetry.usePrometheusNamingis enabled. See OpenTelemetry docs and #9663. Thanks to @andriibeee for the contribution.FEATURE: vmui: improve the Top Queries table UI. Duration columns now display human-readable values (e.g.
1.23s) instead of raw seconds, memory column shows human-readable sizes (e.g.1.23 MB), instant queries are labeled asinstantinstead of empty string, and column headers now show tooltips with descriptions. See #10790.FEATURE: vmagent: drain in-memory remote write queue on shutdown within the 5-second grace period before falling back to persisting blocks to disk. See #9996
FEATURE:
vminsertin VictoriaMetrics cluster: Improve slowness-based rerouting to prevent rerouting storms under high cluster load. Previously, rerouting could cascade across storage nodes when the whole cluster was saturated, making the situation worse. Now rerouting only activates when the cluster p90 saturation is below 60%, and the slowest node is more than 20% slower than p90. See #10876.FEATURE: vmauth: add
{{.MetricsAccountID}}and{{.MetricsProjectID}}JWT claim placeholders for use inheadersandurl_prefixconfig fields. Previously, only the combined{{.MetricsTenant}}(accountID:projectID) JWT placeholder was supported, making it impossible to configure multitenancy via headers. See #10927. Thanks to @Vinayak9769 for the contribution.FEATURE: vmui: display
nullvalues onRaw Querychart.nullvalues can be actualNaNornullvalues exposed by the exporter, or stale markers. Before, vmui Raw Query was silently dropping non-numeric values. Displaying such values on the chart could improve the debugging experience. See #10986.BUGFIX: stream aggregation: stop emitting stale values for
quantiles(...)outputs when a time series has no samples during the current aggregation interval. See #10918. Thanks to @alexei38 for the contribution.BUGFIX: stream aggregation: extend delay on aggregation windows flush by the biggest lag among pushed samples. Before, the delay was calculated as 95th percentile across samples, which could underrepresent outliers and reject them from aggregation as "too old". See #10402.
BUGFIX: vmagent: fix a bug in cardinality limiters where series with different labels, like
{a="bc"}and{ab="c"}, could be incorrectly treated as identical and dropped. See #10937.BUGFIX: vmagent: hide values passed to
-remoteWrite.headersin startup logs,/metrics, and/flags, since they can contain sensitive HTTP headers such asAuthorizationand API keys.BUGFIX: vmagent: hide values passed to
-remoteWrite.proxyURLin startup logs,/metrics, and/flags, since they can contain sensitive credentials.BUGFIX: vmalert: hide values passed to
-remoteWrite.headers,remoteRead.headers,datasource.headersandnotifier.headersin startup logs,/metrics, and/flags, since they can contain sensitive HTTP headers such asAuthorizationand API keys.BUGFIX:
vminsertin VictoriaMetrics cluster: properly establish mtls connection between vmstorage and vminsert. Regression was introduced in v1.130.0 release for the enterprise version of vmstorage. See #10972.BUGFIX: vmrestore: fix a bug where specifying
-storageDataPathwith a trailing slash could causevmrestoreto panic. See #10823. Thanks to @utafrali for the contribution.BUGFIX: vmagent: prevent unintentional rerouting of samples to other sharding targets when one of the
-remoteWrite.urltargets with-remoteWrite.disableOnDiskQueuebecomes blocked. Previously this could break the sharding guarantee by sending samples to wrong targets instead of dropping or retrying them. See #10507.BUGFIX: vmagent: return error on startup if
-remoteWrite.disableOnDiskQueueis not configured uniformly across all-remoteWrite.urltargets when-remoteWrite.shardByURLis enabled. Either all targets must have it enabled or all must have it disabled. See #10507.BUGFIX: vmsingle and
vmselectin VictoriaMetrics cluster: hide values passed tovmalert.proxyURLin startup logs,/metrics, and/flags, since they can contain sensitive HTTP headers such asAuthorizationand API keys.BUGFIX: vmui: preserve exact series values in graph tooltips instead of rounding them by significant digits. See #10952.
BUGFIX: all VictoriaMetrics components: fix int64 overflow when parsing timestamp parameters with relative durations. See #10880.
BUGFIX: vmsingle and
vmstoragein VictoriaMetrics cluster:-denyQueriesOutsideRetentionnow also rejects queries whose end time is beyond-futureRetention. See #10879.BUGFIX: vmui: add missing
__timestamp__and__value__columns to CSV exported from the table view on the Query tab. See #10975.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.