Update victoriametrics/vmagent Docker tag to v1.122.0 #521

2025-07-22T03:07:52Z

renovate commented

2025-07-22 03:07:52 +00:00

This PR contains the following updates:

Package	Update	Change
victoriametrics/vmagent	minor	`v1.121.0` -> `v1.122.0`

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)

`v1.122.0`

Compare Source

v1.122.0

Released at 2025-07-18

Update Note 1: vmsingle and vmstorage in VictoriaMetrics cluster: The -snapshotsMaxAge flag default have been changed to 3d. This enables automatic deletion of snapshots older than 3 days. If you want to keep the previous behavior (never automatically deleting snapshots), please set -snapshotsMaxAge=0. See #9344 for the details.

Update Note 2: all the VictoriaMetrics Enterprise components: -eula command-line flag is skipped when validating VictoriaMetrics enterprise license. Instead, the -license or -licenseFile command-line flags must be used to provide a valid license key. See these docs for configuration examples.

SECURITY: upgrade Go builder from Go1.24.4 to Go1.24.5. See the list of issues addressed in Go1.24.5.
SECURITY: upgrade base docker image (Alpine) from 3.22.0 to 3.22.1. See Alpine 3.22.1 release notes.
FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: enable automatic deletion of snapshots older than 3 days by default. This helps to avoid wasting disk space due to snapshots not being removed in case of backup failure. See #9344.
FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: enable metric names stats tracker by default.
FEATURE: MetricsQL: revert change on respecting staleness markers when calculating rate and increase functions described in #8891-comment. This change was introduced in v1.120.0.
FEATURE: vmselect in VictoriaMetrics cluster: Increase idle timeout from 30s to 2m and ensure at least two connections remain open between vmselect and vmstorage. The change smooth out connection usage during traffic spikes. See #9464.
BUGFIX: all VictoriaMetrics components: properly set process_cpu_cores_available metric to respect both logical CPU cores and cgroup CPU quota. Previously, it could report incorrect values in containerized environments with no cgroup limits. See #9449. Thanks to the @fxrlv.
BUGFIX: vmagent and vmsingle: properly release memory for /target_response API requests. Previously it could used after return and it may lead to data races and potential data loss during scraping. See #9466. Thanks to the @fxrlv.
BUGFIX: vmagent: Prevent panic when re-packing a corrupted block during protocol downgrade. See #9417.
BUGFIX: vmselect in VictoriaMetrics cluster: fix handling of /api/v1/notifiers and /api/v1/metadata endpoints; previously, requests to these endpoints returned 400 Bad Request. vmsingle was not affected.

Configuration

📅 Schedule: 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 is behind base branch, 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 has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [victoriametrics/vmagent](https://github.com/VictoriaMetrics/VictoriaMetrics) | minor | `v1.121.0` -> `v1.122.0` | --- ### Release Notes <details> <summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)</summary> ### [`v1.122.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.122.0) [Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.121.0...v1.122.0) ##### [v1.122.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.122.0) Released at 2025-07-18 **Update Note 1:** [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): The `-snapshotsMaxAge` flag default have been changed to `3d`. This enables automatic deletion of snapshots older than 3 days. If you want to keep the previous behavior (never automatically deleting snapshots), please set `-snapshotsMaxAge=0`. See [#9344](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9344) for the details. **Update Note 2:** all the [VictoriaMetrics Enterprise](https://docs.victoriametrics.com/enterprise.html) components: `-eula` command-line flag is skipped when validating VictoriaMetrics enterprise license. Instead, the `-license` or `-licenseFile` command-line flags must be used to provide a valid license key. See [these docs](https://docs.victoriametrics.com/victoriametrics/enterprise/) for configuration examples. - SECURITY: upgrade Go builder from Go1.24.4 to Go1.24.5. See [the list of issues addressed in Go1.24.5](https://github.com/golang/go/issues?q=milestone%3AGo1.24.5+label%3ACherryPickApproved). - SECURITY: upgrade base docker image (Alpine) from 3.22.0 to 3.22.1. See [Alpine 3.22.1 release notes](https://www.alpinelinux.org/posts/Alpine-3.19.8-3.20.7-3.21.4-3.22.1-released.html). - FEATURE: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): enable automatic deletion of snapshots older than 3 days by default. This helps to avoid wasting disk space due to snapshots not being removed in case of backup failure. See [#9344](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9344). - FEATURE: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): enable [metric names stats tracker](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#track-ingested-metrics-usage) by default. - FEATURE: [MetricsQL](https://docs.victoriametrics.com/victoriametrics/metricsql/): revert change on respecting staleness markers when calculating `rate` and `increase` functions described in [#8891-comment](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8891#issuecomment-2875542721). This change was introduced in [v1.120.0](https://docs.victoriametrics.com/victoriametrics/changelog/#v11200). - FEATURE: [vmselect](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/) in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): Increase idle timeout from `30s` to `2m` and ensure at least two connections remain open between `vmselect` and `vmstorage`. The change smooth out connection usage during traffic spikes. See [#9464](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/9464). - BUGFIX: all VictoriaMetrics components: properly set `process_cpu_cores_available` metric to respect both logical CPU cores and cgroup CPU quota. Previously, it could report incorrect values in containerized environments with no cgroup limits. See [#9449](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/9449). Thanks to the [@fxrlv](https://github.com/fxrlv). - BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent/) and [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/): properly release memory for `/target_response` API requests. Previously it could used after return and it may lead to data races and potential data loss during scraping. See [#9466](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/9466). Thanks to the [@fxrlv](https://github.com/fxrlv). - BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent/): Prevent panic when re-packing a corrupted block during protocol downgrade. See [#9417](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9417). - BUGFIX: `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): fix handling of `/api/v1/notifiers` and `/api/v1/metadata` endpoints; previously, requests to these endpoints returned 400 Bad Request. `vmsingle` was not affected. </details> --- ### Configuration 📅 **Schedule**: 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 is behind base branch, 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 has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

renovate added 1 commit 2025-07-22 03:07:53 +00:00

Update victoriametrics/vmagent Docker tag to v1.122.0 6ddef721ba

AverageMarcus merged commit 6b4ffa50d2 into master

2025-07-22 05:42:54 +00:00

AverageMarcus deleted branch renovate/victoriametrics

2025-07-22 05:42:55 +00:00

AverageMarcus referenced this issue from a commit

2025-07-22 05:42:56 +00:00

Merge pull request 'Update victoriametrics/vmagent Docker tag to v1.122.0' (#521) from renovate/victoriametrics into master

Sign in to join this conversation.