@teambit/harmony.content.cli-reference 2.0.596 → 2.0.597

package/cli-reference.docs.mdx

@@ -1,4 +1,4 @@
 ---
-description: 'Bit command synopses. Bit version: 1.9.109'
+description: 'Bit command synopses. Bit version: 1.9.110'
 labels: ['cli', 'mdx', 'docs']
 ---

package/cli-reference.json

@@ -5125,56 +5125,6 @@
       }
     ]
   },
-  {
-    "name": "update-dependencies <data>",
-    "alias": "",
-    "options": [
-      [
-        "",
-        "tag",
-        "tag once the build is completed (by default it snaps)"
-      ],
-      [
-        "",
-        "simulation",
-        "simulation purpose. should never be pushed"
-      ],
-      [
-        "",
-        "push",
-        "export the updated objects to the original scopes once tagged/snapped"
-      ],
-      [
-        "",
-        "message <string>",
-        "message to be saved as part of the version log"
-      ],
-      [
-        "",
-        "username <string>",
-        "username to be saved as part of the version log"
-      ],
-      [
-        "",
-        "email <string>",
-        "email to be saved as part of the version log"
-      ],
-      [
-        "",
-        "lane <lane-id>",
-        "helps to fetch the components from the lane scope (relevant for --multiple)"
-      ],
-      [
-        "",
-        "skip-new-scope-validation",
-        "avoid throwing an error when running on a non-new scope"
-      ]
-    ],
-    "description": "update dependencies for components and tag/snap the results",
-    "extendedDescription": "this command should be running from a new bare scope, it first imports the components it needs and then processes the update.\nthe input data is a stringified JSON of an array of the following object.\n{\n  componentId: string; // ids always have scope, so it's safe to parse them from string\n  dependencies: string[]; // e.g. [teambit/compiler@1.0.0, teambit/tester@1.0.0]\n  versionToTag?: string; // specific version (e.g. '1.0.0') or semver (e.g. 'minor', 'patch')\n  versionToSnap?: string; // specific hash to snap\n}\nan example of the final data: '[{\"componentId\":\"ci.remote2/comp-b\",\"dependencies\":[\"ci.remote/comp1@0.0.2\"]}]'\n",
-    "group": "development",
-    "private": true
-  },
   {
     "name": "schema <pattern>",
     "alias": "",

package/dist/cli-reference.docs.mdx

@@ -1,4 +1,4 @@
 ---
-description: 'Bit command synopses. Bit version: 1.9.109'
+description: 'Bit command synopses. Bit version: 1.9.110'
 labels: ['cli', 'mdx', 'docs']
 ---

package/dist/cli-reference.json

@@ -5125,56 +5125,6 @@
             }
         ]
     },
-    {
-        "name": "update-dependencies <data>",
-        "alias": "",
-        "options": [
-            [
-                "",
-                "tag",
-                "tag once the build is completed (by default it snaps)"
-            ],
-            [
-                "",
-                "simulation",
-                "simulation purpose. should never be pushed"
-            ],
-            [
-                "",
-                "push",
-                "export the updated objects to the original scopes once tagged/snapped"
-            ],
-            [
-                "",
-                "message <string>",
-                "message to be saved as part of the version log"
-            ],
-            [
-                "",
-                "username <string>",
-                "username to be saved as part of the version log"
-            ],
-            [
-                "",
-                "email <string>",
-                "email to be saved as part of the version log"
-            ],
-            [
-                "",
-                "lane <lane-id>",
-                "helps to fetch the components from the lane scope (relevant for --multiple)"
-            ],
-            [
-                "",
-                "skip-new-scope-validation",
-                "avoid throwing an error when running on a non-new scope"
-            ]
-        ],
-        "description": "update dependencies for components and tag/snap the results",
-        "extendedDescription": "this command should be running from a new bare scope, it first imports the components it needs and then processes the update.\nthe input data is a stringified JSON of an array of the following object.\n{\n  componentId: string; // ids always have scope, so it's safe to parse them from string\n  dependencies: string[]; // e.g. [teambit/compiler@1.0.0, teambit/tester@1.0.0]\n  versionToTag?: string; // specific version (e.g. '1.0.0') or semver (e.g. 'minor', 'patch')\n  versionToSnap?: string; // specific hash to snap\n}\nan example of the final data: '[{\"componentId\":\"ci.remote2/comp-b\",\"dependencies\":[\"ci.remote/comp1@0.0.2\"]}]'\n",
-        "group": "development",
-        "private": true
-    },
     {
         "name": "schema <pattern>",
         "alias": "",