From d775f0c6a4249a3e40a653416978ba3efc21b91e Mon Sep 17 00:00:00 2001
From: "patchback[bot]" <45432694+patchback[bot]@users.noreply.github.com>
Date: Tue, 30 Jun 2026 18:52:39 +0200
Subject: [PATCH] [PR #12367/dda7c1fe backport][stable-12] dnf_versionlock:
 Docs say module incompatible with dnf5 but compatibility was resolved
 (#12370)

dnf_versionlock: Docs say module incompatible with dnf5 but compatibility was resolved (#12367)

Compatibility with dnf5 was resolved in PR 9127

(cherry picked from commit dda7c1fea76e812729efb903119bfaab61275c25)

Co-authored-by: Michael Sprott <165604036+sprottm@users.noreply.github.com>
---
 plugins/modules/dnf_versionlock.py | 1 -
 1 file changed, 1 deletion(-)

diff --git a/plugins/modules/dnf_versionlock.py b/plugins/modules/dnf_versionlock.py
index c6c15fee1a..b7f49ed13f 100644
--- a/plugins/modules/dnf_versionlock.py
+++ b/plugins/modules/dnf_versionlock.py
@@ -57,7 +57,6 @@ notes:
   - In an ideal world, the C(versionlock) plugin would have a dry-run option to know for sure what is going to happen. So
     far we have to work with a best guess as close as possible to the behaviour inferred from its code.
   - For most of cases where you want to lock and unlock specific versions of a package, this works fairly well.
-  - Does not work with C(dnf5).
 requirements:
   - dnf
   - dnf-plugin-versionlock