Skip to content

[Backport release-25.05] victoriametrics: 1.119.0 -> 1.120.0#450719

Closed
nixpkgs-ci[bot] wants to merge 1 commit intorelease-25.05from
backport-419388-to-release-25.05
Closed

[Backport release-25.05] victoriametrics: 1.119.0 -> 1.120.0#450719
nixpkgs-ci[bot] wants to merge 1 commit intorelease-25.05from
backport-419388-to-release-25.05

Conversation

@nixpkgs-ci
Copy link
Contributor

@nixpkgs-ci nixpkgs-ci bot commented Oct 10, 2025

Bot-based backport to release-25.05, triggered by a label in #419388.

  • Before merging, ensure that this backport is acceptable for the release.
    • Even as a non-committer, if you find that it is not acceptable, leave a comment.

@nixpkgs-ci nixpkgs-ci bot mentioned this pull request Oct 10, 2025
13 tasks
@nixpkgs-ci nixpkgs-ci bot added 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 4.workflow: backport This targets a stable branch labels Oct 10, 2025
@nixpkgs-ci nixpkgs-ci bot added the 2.status: merge conflict This PR has merge conflicts with the target branch label Oct 13, 2025
@nixpkgs-ci nixpkgs-ci bot added the 2.status: merge-bot eligible This PR can be merged by commenting "@NixOS/nixpkgs-merge-bot merge". label Nov 2, 2025
@Shawn8901
Copy link
Contributor

#450723 did this backport

@Shawn8901 Shawn8901 closed this Nov 3, 2025
@jopejoe1 jopejoe1 deleted the backport-419388-to-release-25.05 branch November 25, 2025 09:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2.status: merge conflict This PR has merge conflicts with the target branch 2.status: merge-bot eligible This PR can be merged by commenting "@NixOS/nixpkgs-merge-bot merge". 4.workflow: backport This targets a stable branch 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants