diff --git a/images/virt-artifact/patches/024-auto-migrate-if-nodeplacement-changed.patch b/images/virt-artifact/patches/025-auto-migrate-if-nodeplacement-changed.patch
similarity index 100%
rename from images/virt-artifact/patches/024-auto-migrate-if-nodeplacement-changed.patch
rename to images/virt-artifact/patches/025-auto-migrate-if-nodeplacement-changed.patch
diff --git a/images/virt-artifact/patches/README.md b/images/virt-artifact/patches/README.md
index c599721c6..d60bb6e76 100644
--- a/images/virt-artifact/patches/README.md
+++ b/images/virt-artifact/patches/README.md
@@ -84,7 +84,7 @@ Unsuccessful migrations may leave a lot of Pods. These huge lists reduce perform
 Replace the expressions for the ValidatingAdmissionPolicy kubevirt-node-restriction-policy.
 This is necessary because of the kube-api-rewriter that changes the labels.
 
-#### `024-auto-migrate-if-nodeplacement-changed.patch`
+#### `025-auto-migrate-if-nodeplacement-changed.patch`
 
 Start the migration if the nodeSelector or affinity has changed.
 How does it work?