Skip to content

chore(deps): update quay.io/victoriametrics/vmstorage docker tag to v1.148.0#229

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/victoriametrics-default-versions
Open

chore(deps): update quay.io/victoriametrics/vmstorage docker tag to v1.148.0#229
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/victoriametrics-default-versions

Conversation

@renovate

@renovate renovate Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
quay.io/victoriametrics/vmstorage minor v1.147.0v1.148.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

VictoriaMetrics/VictoriaMetrics (quay.io/victoriametrics/vmstorage)

v1.148.0

Compare Source

v1.148.0

Released at 2026-07-17

  • SECURITY: upgrade Go builder from Go1.26.4 to Go1.26.5. See the list of issues addressed in Go1.26.5.

  • FEATURE: MetricsQL: support fill modifiers to allow missing series on either side of a binary operation to be filled with a provided default value. See #​10598.

  • FEATURE: vmagent and vmsingle: support scraping metrics over Unix domain sockets. The socket path can be configured via the __unix_socket__ target label. See #​11156. Thanks to @​vinyas-bharadwaj for contribution.

  • FEATURE: vmagent and vmsingle: Improve background discovery performance for http_sd discovery. See #​8838.

  • FEATURE: vmagent and vmsingle: allow overriding max_scrape_size on a per-target basis via the __max_scrape_size__ label during target relabeling. See #​11188.

  • FEATURE: vmstorage and vmsingle: add -maxBackfillAge command-line flag for limiting ingestion of samples with historical timestamps, for example, when older data has been moved between storage tiers (nvme/hdd, hot/cold). See #​11199. Thanks to @​AshwinRamaniPsg for contribution.

  • FEATURE: vmagent: automatically preload relabeling rules configured via -remoteWrite.relabelConfig and -remoteWrite.urlRelabelConfig in the metrics relabel debug UI. See #​9918.

  • BUGFIX: vminsert in VictoriaMetrics cluster: Now drops metadata blocks when communicating with vmstorage nodes over the legacy RPC protocol. To avoid this limitation, upgrade vmstorage to a version that supports the new RPC protocol (>= v1.137.0). See #​11146.

  • BUGFIX: vmbackup and vmbackupmanager: retry S3 requests failing with HTTP 429 status code or TooManyRequests error code. Previously such requests were not retried, so a short burst of rate limiting would fail the whole backup. See #​11218. Thanks to @​gautamrizwani for contribution.

  • BUGFIX: vmselect in VictoriaMetrics cluster: properly apply limit to metrics metadata response. See #​11139.

  • BUGFIX: vmagent: fix a possible data race when processing OpenTelemetry metadata. See #​11238. Thanks to @​nevgeny for contribution.

  • BUGFIX: vmagent: flush pending persistent queue data to chunk file before updating the metadata. This prevents the metadata writer offset from getting ahead of the chunk file size and avoids losing the persistent queue after an unclean shutdown. See #​11192.

  • BUGFIX: vmagent: atomically write persistent queue metainfo to prevent possible file corruption on ungraceful shutdown. See #​11192.

  • BUGFIX: vmagent: fix increased CPU and memory usage when -remoteWrite.urlRelabelConfig or -remoteWrite.streamAggr.config flags are used. The bug was introduced in #​10854 and existed since v1.147.0. See #​11250.

  • BUGFIX: vmui: preserve newline formatting in alert and rule annotations on the Alerting page. See #​11171.

  • BUGFIX: vmui: hide Total metric names stats on Cardinality Explorer page when user selects a specific metric or label to focus. See #​11154 for details. Thanks to @​lghuy05 for the contribution.

  • BUGFIX: vmui: keep only one header navigation dropdown (Explore, Tools) open at a time. Previously, hovering across two dropdowns could briefly leave both open due to the close delay. See #​11224. Thanks to @​antedotee for contribution.

  • BUGFIX: vmauth: return 408 Request Timeout instead of 400 Bad Request when the request body isn't received within -maxQueueDuration. This prevents vmagent from incorrectly downgrading the remote write protocol and dropping data when vmauth is used as a proxy for a remote write endpoint. See #​11272.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant