From cc31f592cd211aa1d857666c149eb85784b99064 Mon Sep 17 00:00:00 2001
From: schroda <50052685+schroda@users.noreply.github.com>
Date: Tue, 7 Apr 2026 15:06:35 +0200
Subject: [PATCH] Fix saving global metadata applied migration

The applied migration change never got stored on the server because the mutation got excluded due to incorrectly setting the "isMigration" flag to false.
This resulted in executing the missing migration everytime the metadata were read.

Regression 430939a47a82c74e6ef5a8e2bb428b68420e2e66
---
 src/lib/requests/RequestManager.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/lib/requests/RequestManager.ts b/src/lib/requests/RequestManager.ts
index 034221a7..9940ed29 100644
--- a/src/lib/requests/RequestManager.ts
+++ b/src/lib/requests/RequestManager.ts
@@ -1314,7 +1314,7 @@ export class RequestManager {
                 hasPostUpdateDeletions:
                     !!postUpdateDeleteInput.keys?.length || !!postUpdateDeleteInput.prefixes?.length,
                 migrateInput,
-                isMigration: !!updateInput.metas.length,
+                isMigration: !!migrateInput.metas.length,
             },
             {
                 optimisticResponse: {