chore: use yarn lockfile instead of npm one (#314)

Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
Co-authored-by: Francesco Canovai <francesco.canovai@enterprisedb.com>

renovate.json5

@@ -11,6 +11,9 @@
   ],
   rebaseWhen: 'never',
   prConcurrentLimit: 5,
+  lockFileMaintenance: {
+    "enabled": true,
+  },
   "gomod": {
     // Do not manage the dagger go.mod file
     "ignorePaths": [
@@ -100,6 +103,13 @@
       ],
       "groupName": "all sagikazarmark daggerverse dependencies"
     },
+    {
+      matchFileNames: [
+        "web/package.json",
+        "web/yarn.lock"
+      ],
+      groupName: "documentation dependencies"
+    },
     {
       "matchUpdateTypes": [
         "minor",

web/.gitignore

@@ -18,3 +18,4 @@
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
+package-lock.json