balena-cli 23.2.9-build-kyle-dedupe-only-587aec396db5b1a1f89281bd294724f526e322f7-1 → 23.2.9

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "balena-cli",
-  "version": "23.2.9-build-kyle-dedupe-only-587aec396db5b1a1f89281bd294724f526e322f7-1",
+  "version": "23.2.9",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "balena-cli",
-      "version": "23.2.9-build-kyle-dedupe-only-587aec396db5b1a1f89281bd294724f526e322f7-1",
+      "version": "23.2.9",
       "hasInstallScript": true,
       "license": "Apache-2.0",
       "dependencies": {

package/oclif.manifest.json

@@ -160,6 +160,56 @@
         "create.js"
       ]
     },
+    "block:create": {
+      "aliases": [],
+      "args": {
+        "name": {
+          "description": "block name",
+          "name": "name",
+          "required": true
+        }
+      },
+      "description": "Create an block.\n\nCreate a new balena block.\n\nYou can specify the organization the block should belong to using\nthe `--organization` option. The organization's handle, not its name,\nshould be provided. Organization handles can be listed with the\n`balena organization list` command.\n\nThe block's default device type is specified with the `--type` option.\nThe `balena device-type list` command can be used to list the available\ndevice types.\n\nInteractive dropdowns will be shown for selection if no device type or\norganization is specified and there are multiple options to choose from.\nIf there is a single option to choose from, it will be chosen automatically.\nThis interactive behavior can be disabled by explicitly specifying a device\ntype and organization.",
+      "examples": [
+        "$ balena block create MyBlock",
+        "$ balena block create MyBlock --organization mmyorg",
+        "$ balena block create MyBlock -o myorg --type raspberry-pi"
+      ],
+      "flags": {
+        "organization": {
+          "char": "o",
+          "description": "handle of the organization the block should belong to",
+          "name": "organization",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "type": {
+          "char": "t",
+          "description": "block device type (Check available types with `balena device-type list`)",
+          "name": "type",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "block:create",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "block",
+        "create.js"
+      ]
+    },
     "build": {
       "aliases": [],
       "args": {
@@ -362,56 +412,6 @@
         "index.js"
       ]
     },
-    "block:create": {
-      "aliases": [],
-      "args": {
-        "name": {
-          "description": "block name",
-          "name": "name",
-          "required": true
-        }
-      },
-      "description": "Create an block.\n\nCreate a new balena block.\n\nYou can specify the organization the block should belong to using\nthe `--organization` option. The organization's handle, not its name,\nshould be provided. Organization handles can be listed with the\n`balena organization list` command.\n\nThe block's default device type is specified with the `--type` option.\nThe `balena device-type list` command can be used to list the available\ndevice types.\n\nInteractive dropdowns will be shown for selection if no device type or\norganization is specified and there are multiple options to choose from.\nIf there is a single option to choose from, it will be chosen automatically.\nThis interactive behavior can be disabled by explicitly specifying a device\ntype and organization.",
-      "examples": [
-        "$ balena block create MyBlock",
-        "$ balena block create MyBlock --organization mmyorg",
-        "$ balena block create MyBlock -o myorg --type raspberry-pi"
-      ],
-      "flags": {
-        "organization": {
-          "char": "o",
-          "description": "handle of the organization the block should belong to",
-          "name": "organization",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "type": {
-          "char": "t",
-          "description": "block device type (Check available types with `balena device-type list`)",
-          "name": "type",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "block:create",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "block",
-        "create.js"
-      ]
-    },
     "config:generate": {
       "aliases": [],
       "args": {},
@@ -709,253 +709,30 @@
       ]
     },
     "config:write": {
-      "aliases": [],
-      "args": {
-        "key": {
-          "description": "the key of the config parameter to write",
-          "name": "key",
-          "required": true
-        },
-        "value": {
-          "description": "the value of the config parameter to write",
-          "name": "value",
-          "required": true
-        }
-      },
-      "description": "Write a key-value pair to the config.json file of an OS image or attached media.\n\nWrite a key-value pair to the 'config.json' file of a balenaOS image file or\nattached SD card or USB stick.\n\nDocumentation for the balenaOS 'config.json' file can be found at:\nhttps://www.balena.io/docs/reference/OS/configuration/",
-      "examples": [
-        "$ balena config write ntpServers \"0.resinio.pool.ntp.org 1.resinio.pool.ntp.org\"",
-        "$ balena config write --drive /dev/disk2 hostname custom-hostname",
-        "$ balena config write --drive balena.img os.network.connectivity.interval 300"
-      ],
-      "flags": {
-        "drive": {
-          "char": "d",
-          "description": "path to OS image file (e.g. balena.img) or block device (e.g. /dev/disk2)",
-          "name": "drive",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "config:write",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "root": true,
-      "offlineCompatible": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "config",
-        "write.js"
-      ]
-    },
-    "deploy": {
-      "aliases": [],
-      "args": {
-        "fleet": {
-          "description": "fleet name or slug (preferred)",
-          "name": "fleet",
-          "required": true
-        },
-        "image": {
-          "description": "the image to deploy",
-          "name": "image"
-        }
-      },
-      "description": "Deploy a single image or a multicontainer project to a balena fleet.\n\nUsage: `deploy <fleet> ([image] | --build [--source build-dir])`\n\nUse this command to deploy an image or a complete multicontainer project to a\nfleet, optionally building it first. The source images are searched for\n(and optionally built) using the docker daemon in your development machine or\nbalena device. (See also the `balena push` command for the option of building\nthe image in the balenaCloud build servers.)\n\nUnless an image is specified, this command will look into the current directory\n(or the one specified by --source) for a docker-compose.yml file.  If one is\nfound, this command will deploy each service defined in the compose file,\nbuilding it first if an image for it doesn't exist. Image names will be looked\nup according to the scheme: `<projectName>_<serviceName>`.\n\nIf a compose file isn't found, the command will look for a Dockerfile[.template]\nfile (or alternative Dockerfile specified with the `-f` option), and if yet\nthat isn't found, it will try to generate one.\n\nTo deploy to a fleet where you are a collaborator, use fleet slug including the\norganization:  `balena deploy <organization>/<fleet>`.\n\nREGISTRY SECRETS  \nThe --registry-secrets option specifies a JSON or YAML file containing private\nDocker registry usernames and passwords to be used when pulling base images.\nSample registry-secrets YAML file:\n```\n\t'my-registry-server.com:25000':\n\t\tusername: ann\n\t\tpassword: hunter2\n\t'':  # Use the empty string to refer to the Docker Hub\n\t\tusername: mike\n\t\tpassword: cze14\n\t'eu.gcr.io':  # Google Container Registry\n\t\tusername: '_json_key'\n\t\tpassword: '{escaped contents of the GCR keyfile.json file}'\n```\nFor a sample project using registry secrets with the Google Container Registry,\ncheck: https://github.com/balena-io-examples/sample-gcr-registry-secrets\n\nIf the --registry-secrets option is not specified, and a secrets.yml or\nsecrets.json file exists in the balena directory (usually $HOME/.balena),\nthis file will be used instead.\n\nDOCKERIGNORE AND GITIGNORE FILES  \nBy default, the balena CLI will use a single \".dockerignore\" file (if any) at\nthe project root (--source directory) in order to decide which source files to\nexclude from the \"build context\" (tar stream) sent to balenaCloud, Docker\ndaemon or balenaEngine.  In a microservices (multicontainer) fleet, the\nsource directory is the directory that contains the \"docker-compose.yml\" file.\n\nThe --multi-dockerignore (-m) option may be used with microservices\n(multicontainer) fleets that define a docker-compose.yml file. When this\noption is used, each service subdirectory (defined by the `build` or\n`build.context` service properties in the docker-compose.yml file) is\nfiltered separately according to a .dockerignore file defined in the service\nsubdirectory. If no .dockerignore file exists in a service subdirectory, then\nonly the default .dockerignore patterns (see below) apply for that service\nsubdirectory.\n\nWhen the --multi-dockerignore (-m) option is used, the .dockerignore file (if\nany) defined at the overall project root will be used to filter files and\nsubdirectories other than service subdirectories. It will not have any effect\non service subdirectories, whether or not a service subdirectory defines its\nown .dockerignore file. Multiple .dockerignore files are not merged or added\ntogether, and cannot override or extend other files. This behavior maximizes\ncompatibility with the standard docker-compose tool, while still allowing a\nroot .dockerignore file (at the overall project root) to filter files and\nfolders that are outside service subdirectories.\n\nbalena CLI v11 also took .gitignore files into account. This behavior was\ndeprecated in CLI v12 and removed in CLI v13. Please use .dockerignore files\ninstead.\n\nDefault .dockerignore patterns  \nA few default/hardcoded dockerignore patterns are \"merged\" (in memory) with the\npatterns found in the applicable .dockerignore files, in the following order:\n```\n    **/.git\n    < user's patterns from the applicable '.dockerignore' file, if any >\n    !**/.balena\n    !**/.resin\n    !**/Dockerfile\n    !**/Dockerfile.*\n    !**/docker-compose.yml\n```\nThese patterns always apply, whether or not .dockerignore files exist in the\nproject. If necessary, the effect of the `**/.git` pattern may be modified by\nadding exception patterns to the applicable .dockerignore file(s), for example\n`!mysubmodule/.git`. For documentation on pattern format, see:\n- https://docs.docker.com/engine/reference/builder/#dockerignore-file\n- https://www.npmjs.com/package/@balena/dockerignore\n",
-      "examples": [
-        "$ balena deploy myFleet",
-        "$ balena deploy myorg/myfleet --build --source myBuildDir/",
-        "$ balena deploy myorg/myfleet --build --source myBuildDir/ --note \"this is the note for this release\"",
-        "$ balena deploy myorg/myfleet myRepo/myImage",
-        "$ balena deploy myFleet myRepo/myImage --release-tag key1 \"\" key2 \"value2 with spaces\""
-      ],
-      "flags": {
-        "source": {
-          "char": "s",
-          "description": "specify an alternate source directory; default is the working directory",
-          "name": "source",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "build": {
-          "char": "b",
-          "description": "force a rebuild before deploy",
-          "name": "build",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "nologupload": {
-          "description": "don't upload build logs to the dashboard with image (if building)",
-          "name": "nologupload",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "release-tag": {
-          "description": "Set release tags if the image deployment is successful. Multiple\narguments may be provided, alternating tag keys and values (see examples).\nHint: Empty values may be specified with \"\" (bash, cmd.exe) or '\"\"' (PowerShell).",
-          "name": "release-tag",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "draft": {
-          "description": "Deploy the release as a draft. Draft releases are ignored\nby the 'track latest' release policy but can be used through release pinning.\nDraft releases can be marked as final through the API. Releases are created\nas final by default unless this option is given.",
-          "name": "draft",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "note": {
-          "description": "The notes for this release",
-          "name": "note",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "emulated": {
-          "char": "e",
-          "description": "Use QEMU for ARM architecture emulation during the image build",
-          "name": "emulated",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "dockerfile": {
-          "description": "Alternative Dockerfile name/path, relative to the source folder",
-          "name": "dockerfile",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "nologs": {
-          "description": "Hide the image build log output (produce less verbose output)",
-          "name": "nologs",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "multi-dockerignore": {
-          "char": "m",
-          "description": "Have each service use its own .dockerignore file. See \"balena help build\".",
-          "name": "multi-dockerignore",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "noparent-check": {
-          "description": "Disable project validation check of 'docker-compose.yml' file in parent folder",
-          "name": "noparent-check",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "registry-secrets": {
-          "char": "R",
-          "description": "Path to a YAML or JSON file with passwords for a private Docker registry",
-          "name": "registry-secrets",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "noconvert-eol": {
-          "description": "Don't convert line endings from CRLF (Windows format) to LF (Unix format).",
-          "name": "noconvert-eol",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "projectName": {
-          "char": "n",
-          "description": "Name prefix for locally built images. This is the 'projectName' portion\nin 'projectName_serviceName:tag'. The default is the directory name.",
-          "name": "projectName",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "tag": {
-          "char": "t",
-          "description": "Tag locally built Docker images. This is the 'tag' portion\nin 'projectName_serviceName:tag'. The default is 'latest'.",
-          "name": "tag",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "buildArg": {
-          "char": "B",
-          "description": "[Deprecated] Set a build-time variable (eg. \"-B 'ARG=value'\"). Can be specified multiple times.",
-          "name": "buildArg",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "cache-from": {
-          "description": "Comma-separated list (no spaces) of image names for build cache resolution. Implements the same feature as the \"docker build --cache-from\" option.",
-          "name": "cache-from",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "nocache": {
-          "description": "Don't use docker layer caching when building",
-          "name": "nocache",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "pull": {
-          "description": "Pull the base images again even if they exist locally",
-          "name": "pull",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "squash": {
-          "description": "Squash newly built layers into a single new layer",
-          "name": "squash",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "docker": {
-          "char": "P",
-          "description": "Path to a local docker socket (e.g. /var/run/docker.sock)",
-          "name": "docker",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "dockerHost": {
-          "char": "h",
-          "description": "Docker daemon hostname or IP address (dev machine or balena device) ",
-          "name": "dockerHost",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "dockerPort": {
-          "char": "p",
-          "description": "Docker daemon TCP port number (hint: 2375 for balena devices)",
-          "name": "dockerPort",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "ca": {
-          "description": "Docker host TLS certificate authority file",
-          "name": "ca",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "cert": {
-          "description": "Docker host TLS certificate file",
-          "name": "cert",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
+      "aliases": [],
+      "args": {
         "key": {
-          "description": "Docker host TLS key file",
+          "description": "the key of the config parameter to write",
           "name": "key",
+          "required": true
+        },
+        "value": {
+          "description": "the value of the config parameter to write",
+          "name": "value",
+          "required": true
+        }
+      },
+      "description": "Write a key-value pair to the config.json file of an OS image or attached media.\n\nWrite a key-value pair to the 'config.json' file of a balenaOS image file or\nattached SD card or USB stick.\n\nDocumentation for the balenaOS 'config.json' file can be found at:\nhttps://www.balena.io/docs/reference/OS/configuration/",
+      "examples": [
+        "$ balena config write ntpServers \"0.resinio.pool.ntp.org 1.resinio.pool.ntp.org\"",
+        "$ balena config write --drive /dev/disk2 hostname custom-hostname",
+        "$ balena config write --drive balena.img os.network.connectivity.interval 300"
+      ],
+      "flags": {
+        "drive": {
+          "char": "d",
+          "description": "path to OS image file (e.g. balena.img) or block device (e.g. /dev/disk2)",
+          "name": "drive",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -963,20 +740,20 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "deploy",
+      "id": "config:write",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "authenticated": true,
-      "primary": true,
+      "root": true,
+      "offlineCompatible": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "deploy",
-        "index.js"
+        "config",
+        "write.js"
       ]
     },
     "device-type:list": {
@@ -2537,6 +2314,229 @@
         "set.js"
       ]
     },
+    "deploy": {
+      "aliases": [],
+      "args": {
+        "fleet": {
+          "description": "fleet name or slug (preferred)",
+          "name": "fleet",
+          "required": true
+        },
+        "image": {
+          "description": "the image to deploy",
+          "name": "image"
+        }
+      },
+      "description": "Deploy a single image or a multicontainer project to a balena fleet.\n\nUsage: `deploy <fleet> ([image] | --build [--source build-dir])`\n\nUse this command to deploy an image or a complete multicontainer project to a\nfleet, optionally building it first. The source images are searched for\n(and optionally built) using the docker daemon in your development machine or\nbalena device. (See also the `balena push` command for the option of building\nthe image in the balenaCloud build servers.)\n\nUnless an image is specified, this command will look into the current directory\n(or the one specified by --source) for a docker-compose.yml file.  If one is\nfound, this command will deploy each service defined in the compose file,\nbuilding it first if an image for it doesn't exist. Image names will be looked\nup according to the scheme: `<projectName>_<serviceName>`.\n\nIf a compose file isn't found, the command will look for a Dockerfile[.template]\nfile (or alternative Dockerfile specified with the `-f` option), and if yet\nthat isn't found, it will try to generate one.\n\nTo deploy to a fleet where you are a collaborator, use fleet slug including the\norganization:  `balena deploy <organization>/<fleet>`.\n\nREGISTRY SECRETS  \nThe --registry-secrets option specifies a JSON or YAML file containing private\nDocker registry usernames and passwords to be used when pulling base images.\nSample registry-secrets YAML file:\n```\n\t'my-registry-server.com:25000':\n\t\tusername: ann\n\t\tpassword: hunter2\n\t'':  # Use the empty string to refer to the Docker Hub\n\t\tusername: mike\n\t\tpassword: cze14\n\t'eu.gcr.io':  # Google Container Registry\n\t\tusername: '_json_key'\n\t\tpassword: '{escaped contents of the GCR keyfile.json file}'\n```\nFor a sample project using registry secrets with the Google Container Registry,\ncheck: https://github.com/balena-io-examples/sample-gcr-registry-secrets\n\nIf the --registry-secrets option is not specified, and a secrets.yml or\nsecrets.json file exists in the balena directory (usually $HOME/.balena),\nthis file will be used instead.\n\nDOCKERIGNORE AND GITIGNORE FILES  \nBy default, the balena CLI will use a single \".dockerignore\" file (if any) at\nthe project root (--source directory) in order to decide which source files to\nexclude from the \"build context\" (tar stream) sent to balenaCloud, Docker\ndaemon or balenaEngine.  In a microservices (multicontainer) fleet, the\nsource directory is the directory that contains the \"docker-compose.yml\" file.\n\nThe --multi-dockerignore (-m) option may be used with microservices\n(multicontainer) fleets that define a docker-compose.yml file. When this\noption is used, each service subdirectory (defined by the `build` or\n`build.context` service properties in the docker-compose.yml file) is\nfiltered separately according to a .dockerignore file defined in the service\nsubdirectory. If no .dockerignore file exists in a service subdirectory, then\nonly the default .dockerignore patterns (see below) apply for that service\nsubdirectory.\n\nWhen the --multi-dockerignore (-m) option is used, the .dockerignore file (if\nany) defined at the overall project root will be used to filter files and\nsubdirectories other than service subdirectories. It will not have any effect\non service subdirectories, whether or not a service subdirectory defines its\nown .dockerignore file. Multiple .dockerignore files are not merged or added\ntogether, and cannot override or extend other files. This behavior maximizes\ncompatibility with the standard docker-compose tool, while still allowing a\nroot .dockerignore file (at the overall project root) to filter files and\nfolders that are outside service subdirectories.\n\nbalena CLI v11 also took .gitignore files into account. This behavior was\ndeprecated in CLI v12 and removed in CLI v13. Please use .dockerignore files\ninstead.\n\nDefault .dockerignore patterns  \nA few default/hardcoded dockerignore patterns are \"merged\" (in memory) with the\npatterns found in the applicable .dockerignore files, in the following order:\n```\n    **/.git\n    < user's patterns from the applicable '.dockerignore' file, if any >\n    !**/.balena\n    !**/.resin\n    !**/Dockerfile\n    !**/Dockerfile.*\n    !**/docker-compose.yml\n```\nThese patterns always apply, whether or not .dockerignore files exist in the\nproject. If necessary, the effect of the `**/.git` pattern may be modified by\nadding exception patterns to the applicable .dockerignore file(s), for example\n`!mysubmodule/.git`. For documentation on pattern format, see:\n- https://docs.docker.com/engine/reference/builder/#dockerignore-file\n- https://www.npmjs.com/package/@balena/dockerignore\n",
+      "examples": [
+        "$ balena deploy myFleet",
+        "$ balena deploy myorg/myfleet --build --source myBuildDir/",
+        "$ balena deploy myorg/myfleet --build --source myBuildDir/ --note \"this is the note for this release\"",
+        "$ balena deploy myorg/myfleet myRepo/myImage",
+        "$ balena deploy myFleet myRepo/myImage --release-tag key1 \"\" key2 \"value2 with spaces\""
+      ],
+      "flags": {
+        "source": {
+          "char": "s",
+          "description": "specify an alternate source directory; default is the working directory",
+          "name": "source",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "build": {
+          "char": "b",
+          "description": "force a rebuild before deploy",
+          "name": "build",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "nologupload": {
+          "description": "don't upload build logs to the dashboard with image (if building)",
+          "name": "nologupload",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "release-tag": {
+          "description": "Set release tags if the image deployment is successful. Multiple\narguments may be provided, alternating tag keys and values (see examples).\nHint: Empty values may be specified with \"\" (bash, cmd.exe) or '\"\"' (PowerShell).",
+          "name": "release-tag",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "draft": {
+          "description": "Deploy the release as a draft. Draft releases are ignored\nby the 'track latest' release policy but can be used through release pinning.\nDraft releases can be marked as final through the API. Releases are created\nas final by default unless this option is given.",
+          "name": "draft",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "note": {
+          "description": "The notes for this release",
+          "name": "note",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "emulated": {
+          "char": "e",
+          "description": "Use QEMU for ARM architecture emulation during the image build",
+          "name": "emulated",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "dockerfile": {
+          "description": "Alternative Dockerfile name/path, relative to the source folder",
+          "name": "dockerfile",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "nologs": {
+          "description": "Hide the image build log output (produce less verbose output)",
+          "name": "nologs",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "multi-dockerignore": {
+          "char": "m",
+          "description": "Have each service use its own .dockerignore file. See \"balena help build\".",
+          "name": "multi-dockerignore",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "noparent-check": {
+          "description": "Disable project validation check of 'docker-compose.yml' file in parent folder",
+          "name": "noparent-check",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "registry-secrets": {
+          "char": "R",
+          "description": "Path to a YAML or JSON file with passwords for a private Docker registry",
+          "name": "registry-secrets",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "noconvert-eol": {
+          "description": "Don't convert line endings from CRLF (Windows format) to LF (Unix format).",
+          "name": "noconvert-eol",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "projectName": {
+          "char": "n",
+          "description": "Name prefix for locally built images. This is the 'projectName' portion\nin 'projectName_serviceName:tag'. The default is the directory name.",
+          "name": "projectName",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "tag": {
+          "char": "t",
+          "description": "Tag locally built Docker images. This is the 'tag' portion\nin 'projectName_serviceName:tag'. The default is 'latest'.",
+          "name": "tag",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "buildArg": {
+          "char": "B",
+          "description": "[Deprecated] Set a build-time variable (eg. \"-B 'ARG=value'\"). Can be specified multiple times.",
+          "name": "buildArg",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "cache-from": {
+          "description": "Comma-separated list (no spaces) of image names for build cache resolution. Implements the same feature as the \"docker build --cache-from\" option.",
+          "name": "cache-from",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "nocache": {
+          "description": "Don't use docker layer caching when building",
+          "name": "nocache",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "pull": {
+          "description": "Pull the base images again even if they exist locally",
+          "name": "pull",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "squash": {
+          "description": "Squash newly built layers into a single new layer",
+          "name": "squash",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "docker": {
+          "char": "P",
+          "description": "Path to a local docker socket (e.g. /var/run/docker.sock)",
+          "name": "docker",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "dockerHost": {
+          "char": "h",
+          "description": "Docker daemon hostname or IP address (dev machine or balena device) ",
+          "name": "dockerHost",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "dockerPort": {
+          "char": "p",
+          "description": "Docker daemon TCP port number (hint: 2375 for balena devices)",
+          "name": "dockerPort",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "ca": {
+          "description": "Docker host TLS certificate authority file",
+          "name": "ca",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "cert": {
+          "description": "Docker host TLS certificate file",
+          "name": "cert",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "key": {
+          "description": "Docker host TLS key file",
+          "name": "key",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "deploy",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "primary": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "deploy",
+        "index.js"
+      ]
+    },
     "fleet:create": {
       "aliases": [],
       "args": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "balena-cli",
-  "version": "23.2.9-build-kyle-dedupe-only-587aec396db5b1a1f89281bd294724f526e322f7-1",
+  "version": "23.2.9",
   "description": "The official balena Command Line Interface",
   "main": "./build/app.js",
   "homepage": "https://github.com/balena-io/balena-cli",
@@ -262,6 +262,6 @@
     "balena-request": "14.0.6"
   },
   "versionist": {
-    "publishedAt": "2025-12-12T15:41:53.508Z"
+    "publishedAt": "2025-12-12T18:18:37.405Z"
   }
 }