From 19e38dade40fc54ad1f6b7b2b71f34ecd59420e4 Mon Sep 17 00:00:00 2001
From: oxmc7769 <oxmc7769.mail@gmail.com>
Date: Sun, 5 Jul 2026 05:25:55 -0700
Subject: [PATCH] fix: remove invalid updateMany option in moveMultipleFiles

{ new: true } only applies to findOneAndUpdate, not updateMany - it was
always a silent no-op here. Harmless until a stricter mongoose/mongodb
type resolution (no lockfile is committed, so installs float) rejected
it outright, breaking `npm run build` inside the Docker image.
---
 backend/db/mongoDB/fileDB.ts | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/backend/db/mongoDB/fileDB.ts b/backend/db/mongoDB/fileDB.ts
index d75fd4c..1dcfae6 100644
--- a/backend/db/mongoDB/fileDB.ts
+++ b/backend/db/mongoDB/fileDB.ts
@@ -357,8 +357,7 @@ class DbUtil implements IFileDB {
           "metadata.parent": newParent,
           "metadata.parentList": newParentList,
         },
-      },
-      { new: true }
+      }
     );
   };