Skip to content

[Backport release-25.11] knot-resolver-manager_6: 6.1.0 -> 6.2.0#486905

Merged
vcunat merged 1 commit intostaging-next-25.11from
backport-486532-to-release-25.11
Feb 6, 2026
Merged

[Backport release-25.11] knot-resolver-manager_6: 6.1.0 -> 6.2.0#486905
vcunat merged 1 commit intostaging-next-25.11from
backport-486532-to-release-25.11

Conversation

@nixpkgs-ci
Copy link
Contributor

@nixpkgs-ci nixpkgs-ci bot commented Feb 4, 2026

Bot-based backport to release-25.11, triggered by a label in #486532.

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.

Tip

If you maintain all packages touched by this pull request, and they are all located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this PR using the nixpkgs-merge-bot.

https://gitlab.nic.cz/knot/knot-resolver/-/releases/v6.2.0
The enablement of DoQ costs us only 48 KiB of runtime closure increase,
thanks to sharing the costs with knot-dns libs.

(cherry picked from commit 9a49c1f)
@nixpkgs-ci nixpkgs-ci bot mentioned this pull request Feb 4, 2026
13 tasks
@nixpkgs-ci nixpkgs-ci bot added 8.has: package (update) This PR updates a package to a newer version 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. 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 labels Feb 4, 2026
@vcunat
Copy link
Member

vcunat commented Feb 4, 2026

I believe we do want to backport changes like that, though it could be after some delay perhaps.

Copy link
Member

@leona-ya leona-ya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I agree.

@nixpkgs-ci nixpkgs-ci bot added 12.approvals: 1 This PR was reviewed and approved by one person. 12.approved-by: package-maintainer This PR was reviewed and approved by a maintainer listed in any of the changed packages. labels Feb 4, 2026
@vcunat vcunat changed the base branch from release-25.11 to staging-next-25.11 February 6, 2026 18:44
@vcunat vcunat added this pull request to the merge queue Feb 6, 2026
@nixpkgs-ci nixpkgs-ci bot closed this Feb 6, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to a manual request Feb 6, 2026
@nixpkgs-ci nixpkgs-ci bot reopened this Feb 6, 2026
@vcunat vcunat added this pull request to the merge queue Feb 6, 2026
Merged via the queue into staging-next-25.11 with commit 0f68507 Feb 6, 2026
61 of 63 checks passed
@vcunat vcunat deleted the backport-486532-to-release-25.11 branch February 6, 2026 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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 8.has: package (update) This PR updates a package to a newer version 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. 12.approvals: 1 This PR was reviewed and approved by one person. 12.approved-by: package-maintainer This PR was reviewed and approved by a maintainer listed in any of the changed packages.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants