balena-cli 22.2.0 → 22.2.1

package/CHANGELOG.md

@@ -4,7 +4,11 @@ All notable changes to this project will be documented in this file
 automatically by Versionist. DO NOT EDIT THIS FILE MANUALLY!
 This project adheres to [Semantic Versioning](http://semver.org/).
 
-## 22.2.0 - 2025-08-04
+## 22.2.1 - 2025-08-06
+
+* Fix finalize step oclif promote command [Otavio Jacobi]
+
+## 22.2.0 - 2025-08-05
 
 * Upload built assets to s3 as standard oclif packages [Otavio Jacobi]
 

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "balena-cli",
-  "version": "22.2.0",
+  "version": "22.2.1",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "balena-cli",
-      "version": "22.2.0",
+      "version": "22.2.1",
       "hasInstallScript": true,
       "license": "Apache-2.0",
       "dependencies": {
@@ -15883,9 +15883,9 @@
       "integrity": "sha512-y6OAwoSIf7FyjMIv94u+b5rdheZEjzR63GTyZJm5qh4Bi+2YgwLCcI/fPFZkL5PSixOt6ZNKm+w+Hfp/Bciwow=="
     },
     "node_modules/fs-extra": {
-      "version": "11.3.0",
-      "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-11.3.0.tgz",
-      "integrity": "sha512-Z4XaCL6dUDHfP/jT25jJKMmtxvuwbkrD1vNSMFlo9lNLY2c5FHYSQgHPRZUjAB26TpDEoW9HCOgplrdbaPV/ew==",
+      "version": "11.3.1",
+      "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-11.3.1.tgz",
+      "integrity": "sha512-eXvGGwZ5CL17ZSwHWd3bbgk7UUpF6IFHtP57NYYakPvHOs8GDgDe5KJI36jIJzDkJ6eJjuzRA8eBQb6SkKue0g==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
@@ -20427,9 +20427,9 @@
       }
     },
     "node_modules/patch-package/node_modules/yaml": {
-      "version": "2.8.0",
-      "resolved": "https://registry.npmjs.org/yaml/-/yaml-2.8.0.tgz",
-      "integrity": "sha512-4lLa/EcQCB0cJkyts+FpIRx5G/llPxfP6VQU5KByHEhLxY3IJCH0f0Hy1MHI8sClTvsIb8qwRJ6R/ZdlDJ/leQ==",
+      "version": "2.8.1",
+      "resolved": "https://registry.npmjs.org/yaml/-/yaml-2.8.1.tgz",
+      "integrity": "sha512-lcYcMxX2PO9XMGvAJkJ3OsNMw+/7FKes7/hgerGUYWIoWu5j/+YQqcZr5JnPZWzOsEBgMbSbiSTn/dv/69Mkpw==",
       "license": "ISC",
       "bin": {
         "yaml": "bin.mjs"
@@ -23122,9 +23122,10 @@
       }
     },
     "node_modules/tmp": {
-      "version": "0.2.3",
-      "resolved": "https://registry.npmjs.org/tmp/-/tmp-0.2.3.tgz",
-      "integrity": "sha512-nZD7m9iCPC5g0pYmcaxogYKggSfLsdxl8of3Q/oIbqCqLLIO9IAF0GWjX1z9NZRHPiXv8Wex4yDCaZsgEw0Y8w==",
+      "version": "0.2.4",
+      "resolved": "https://registry.npmjs.org/tmp/-/tmp-0.2.4.tgz",
+      "integrity": "sha512-UdiSoX6ypifLmrfQ/XfiawN6hkjSBpCjhKxxZcWlUUmoXLaCKQU0bx4HF/tdDK2uzRuchf1txGvrWBzYREssoQ==",
+      "license": "MIT",
       "engines": {
         "node": ">=14.14"
       }

package/oclif.manifest.json

@@ -163,34 +163,186 @@
         "create.js"
       ]
     },
-    "block:create": {
+    "build": {
       "aliases": [],
       "args": {
-        "name": {
-          "description": "block name",
-          "name": "name",
-          "required": true
+        "source": {
+          "description": "path of project source directory",
+          "name": "source"
         }
       },
-      "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.",
+      "description": "Build a project locally.\n\nUse this command to build an image or a complete multicontainer project with\nthe provided docker daemon in your development machine or balena device.\n(See also the `balena push` command for the option of building images in the\nbalenaCloud build servers.)\n\nYou must specify either a fleet, or the device type and architecture.\n\nThis command will look into the given source directory (or the current working\ndirectory if one isn't specified) for a docker-compose.yml file, and if found,\neach service defined in the compose file will be built. If a compose file isn't\nfound, it will look for a Dockerfile[.template] file (or alternative Dockerfile\nspecified with the `--dockerfile` option), and if no dockerfile is found, it\nwill try to generate one.\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 block create MyBlock",
-        "$ balena block create MyBlock --organization mmyorg",
-        "$ balena block create MyBlock -o myorg --type raspberry-pi"
+        "$ balena build --fleet myFleet",
+        "$ balena build ./source/ --fleet myorg/myfleet",
+        "$ balena build --deviceType raspberrypi3 --emulated",
+        "$ balena build --deviceType raspberrypi3 --arch armv7hf --emulated",
+        "$ balena build --docker /var/run/docker.sock --fleet myFleet   # Linux, Mac",
+        "$ balena build --docker //./pipe/docker_engine --fleet myFleet # Windows",
+        "$ balena build --dockerHost my.docker.host --dockerPort 2376 --ca ca.pem --key key.pem --cert cert.pem -f myFleet"
       ],
       "flags": {
-        "organization": {
-          "char": "o",
-          "description": "handle of the organization the block should belong to",
-          "name": "organization",
+        "arch": {
+          "char": "A",
+          "description": "the architecture to build for",
+          "name": "arch",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "type": {
+        "deviceType": {
+          "char": "d",
+          "description": "the type of device this build is for",
+          "name": "deviceType",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "fleet": {
+          "char": "f",
+          "description": "fleet name or slug (preferred)",
+          "name": "fleet",
+          "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": "block device type (Check available types with `balena device-type list`)",
-          "name": "type",
+          "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"
@@ -198,19 +350,19 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "block:create",
+      "id": "build",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "authenticated": true,
+      "primary": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "block",
-        "create.js"
+        "build",
+        "index.js"
       ]
     },
     "config:generate": {
@@ -557,186 +709,34 @@
         "write.js"
       ]
     },
-    "build": {
+    "block:create": {
       "aliases": [],
       "args": {
-        "source": {
-          "description": "path of project source directory",
-          "name": "source"
+        "name": {
+          "description": "block name",
+          "name": "name",
+          "required": true
         }
       },
-      "description": "Build a project locally.\n\nUse this command to build an image or a complete multicontainer project with\nthe provided docker daemon in your development machine or balena device.\n(See also the `balena push` command for the option of building images in the\nbalenaCloud build servers.)\n\nYou must specify either a fleet, or the device type and architecture.\n\nThis command will look into the given source directory (or the current working\ndirectory if one isn't specified) for a docker-compose.yml file, and if found,\neach service defined in the compose file will be built. If a compose file isn't\nfound, it will look for a Dockerfile[.template] file (or alternative Dockerfile\nspecified with the `--dockerfile` option), and if no dockerfile is found, it\nwill try to generate one.\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",
+      "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 build --fleet myFleet",
-        "$ balena build ./source/ --fleet myorg/myfleet",
-        "$ balena build --deviceType raspberrypi3 --emulated",
-        "$ balena build --deviceType raspberrypi3 --arch armv7hf --emulated",
-        "$ balena build --docker /var/run/docker.sock --fleet myFleet   # Linux, Mac",
-        "$ balena build --docker //./pipe/docker_engine --fleet myFleet # Windows",
-        "$ balena build --dockerHost my.docker.host --dockerPort 2376 --ca ca.pem --key key.pem --cert cert.pem -f myFleet"
+        "$ balena block create MyBlock",
+        "$ balena block create MyBlock --organization mmyorg",
+        "$ balena block create MyBlock -o myorg --type raspberry-pi"
       ],
       "flags": {
-        "arch": {
-          "char": "A",
-          "description": "the architecture to build for",
-          "name": "arch",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "deviceType": {
-          "char": "d",
-          "description": "the type of device this build is for",
-          "name": "deviceType",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "fleet": {
-          "char": "f",
-          "description": "fleet name or slug (preferred)",
-          "name": "fleet",
-          "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",
+        "organization": {
+          "char": "o",
+          "description": "handle of the organization the block should belong to",
+          "name": "organization",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "tag": {
+        "type": {
           "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",
+          "description": "block device type (Check available types with `balena device-type list`)",
+          "name": "type",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -744,19 +744,19 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "build",
+      "id": "block:create",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "primary": true,
+      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "build",
-        "index.js"
+        "block",
+        "create.js"
       ]
     },
     "deploy": {
@@ -3686,136 +3686,6 @@
         "versions.js"
       ]
     },
-    "preload": {
-      "aliases": [],
-      "args": {
-        "image": {
-          "description": "the image file path",
-          "name": "image",
-          "required": true
-        }
-      },
-      "description": "Preload a release on a disk image (or Edison zip archive).\n\nPreload a release (service images/containers) from a balena fleet, and optionally\na balenaOS splash screen, in a previously downloaded '.img' balenaOS image file\nin the local disk (a zip file is only accepted for the Intel Edison device type).\nAfter preloading, the balenaOS image file can be flashed to a device's SD card.\nWhen the device boots, it will not need to download the release, as it was\npreloaded. This is usually combined with release pinning\n(https://www.balena.io/docs/learn/deploy/release-strategy/release-policy/)\nto avoid the device downloading a newer release straight away, if available.\nCheck also the Preloading and Preregistering section of the balena CLI's advanced\nmasterclass document:\nhttps://www.balena.io/docs/learn/more/masterclasses/advanced-cli/#5-preloading-and-preregistering\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).\n\nNote that the this command requires Docker to be installed, as further detailed\nin the balena CLI's installation instructions:\nhttps://github.com/balena-io/balena-cli/blob/master/INSTALL.md\nThe `--dockerHost` and `--dockerPort` flags allow a remote Docker engine to\nbe used, however the image file must be accessible to the remote Docker engine\non the same path given on the command line. This is because Docker's bind mount\nfeature is used to \"share\" the image with a container that performs the preload.",
-      "examples": [
-        "$ balena preload balena.img --fleet MyFleet --commit e1f2592fc6ee949e68756d4f4a48e49bff8d72a0",
-        "$ balena preload balena.img --fleet myorg/myfleet --splash-image image.png",
-        "$ balena preload balena.img"
-      ],
-      "flags": {
-        "fleet": {
-          "char": "f",
-          "description": "fleet name or slug (preferred)",
-          "name": "fleet",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "commit": {
-          "char": "c",
-          "description": "The commit hash of the release to preload. Use \"current\" to specify the current\nrelease (ignored if no appId is given). The current release is usually also the\nlatest, but can be pinned to a specific release. See:\nhttps://www.balena.io/docs/learn/deploy/release-strategy/release-policy/\nhttps://www.balena.io/docs/learn/more/masterclasses/fleet-management/#63-pin-using-the-api\nhttps://github.com/balena-io-examples/staged-releases",
-          "name": "commit",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "splash-image": {
-          "char": "s",
-          "description": "path to a png image to replace the splash screen",
-          "name": "splash-image",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "dont-check-arch": {
-          "description": "disable architecture compatibility check between image and fleet",
-          "name": "dont-check-arch",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "pin-device-to-release": {
-          "char": "p",
-          "description": "pin the preloaded device to the preloaded release on provision",
-          "name": "pin-device-to-release",
-          "allowNo": true,
-          "type": "boolean"
-        },
-        "additional-space": {
-          "description": "expand the image by this amount of bytes instead of automatically estimating the required amount",
-          "name": "additional-space",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "add-certificate": {
-          "description": "Add the given certificate (in PEM format) to /etc/ssl/certs in the preloading container.\nThe file name must end with '.crt' and must not be already contained in the preloader's\n/etc/ssl/certs folder.\nCan be repeated to add multiple certificates.",
-          "name": "add-certificate",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "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": {
-          "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": "preload",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "primary": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "preload",
-        "index.js"
-      ]
-    },
     "push": {
       "aliases": [],
       "args": {
@@ -3886,79 +3756,208 @@
           "allowNo": false,
           "type": "boolean"
         },
-        "registry-secrets": {
-          "char": "R",
-          "description": "Path to a local YAML or JSON file containing Docker registry passwords used\nto pull base images. Note that if registry-secrets are not provided on the\ncommand line, a secrets configuration file from the balena directory will be\nused (usually $HOME/.balena/secrets.yml|.json)",
-          "name": "registry-secrets",
+        "registry-secrets": {
+          "char": "R",
+          "description": "Path to a local YAML or JSON file containing Docker registry passwords used\nto pull base images. Note that if registry-secrets are not provided on the\ncommand line, a secrets configuration file from the balena directory will be\nused (usually $HOME/.balena/secrets.yml|.json)",
+          "name": "registry-secrets",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "nolive": {
+          "description": "Don't run a live session on this push. The filesystem will not be monitored,\nand changes will not be synchronized to any running containers. Note that both\nthis flag and --detached are required to cause the process to end once the\ninitial build has completed.",
+          "name": "nolive",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "detached": {
+          "char": "d",
+          "description": "When pushing to the cloud, this option will cause the build to start, then\nreturn execution back to the shell, with the status and release ID (if\napplicable).  When pushing to a local mode device, this option will cause\nthe command to not tail logs when the build has completed.",
+          "name": "detached",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "service": {
+          "description": "Reject logs not originating from this service.\nThis can be used in combination with --system and other --service flags.\nOnly valid when pushing to a local mode device.",
+          "name": "service",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "system": {
+          "description": "Only show system logs. This can be used in combination with --service.\nOnly valid when pushing to a local mode device.",
+          "name": "system",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "env": {
+          "description": "When performing a push to device, run the built containers with environment\nvariables provided with this argument. Environment variables can be applied\nto individual services by adding their service name before the argument,\nseparated by a colon, e.g:\n\t--env main:MY_ENV=value\nNote that if the service name cannot be found in the composition, the entire\nleft hand side of the = character will be treated as the variable name.",
+          "name": "env",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "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"
+        },
+        "multi-dockerignore": {
+          "char": "m",
+          "description": "Have each service use its own .dockerignore file. See \"balena help push\".",
+          "name": "multi-dockerignore",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "release-tag": {
+          "description": "Set release tags if the image build is successful (balenaCloud only). Multiple\narguments may be provided, alternating tag keys and values (see examples).\nHint: Empty values may be specified with \"\" (bash, cmd.exe) or '\"\"' (PowerShell).",
+          "exclusive": [
+            "detached"
+          ],
+          "name": "release-tag",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "draft": {
+          "description": "Instruct the builder to create 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"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "push",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "primary": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "push",
+        "index.js"
+      ]
+    },
+    "preload": {
+      "aliases": [],
+      "args": {
+        "image": {
+          "description": "the image file path",
+          "name": "image",
+          "required": true
+        }
+      },
+      "description": "Preload a release on a disk image (or Edison zip archive).\n\nPreload a release (service images/containers) from a balena fleet, and optionally\na balenaOS splash screen, in a previously downloaded '.img' balenaOS image file\nin the local disk (a zip file is only accepted for the Intel Edison device type).\nAfter preloading, the balenaOS image file can be flashed to a device's SD card.\nWhen the device boots, it will not need to download the release, as it was\npreloaded. This is usually combined with release pinning\n(https://www.balena.io/docs/learn/deploy/release-strategy/release-policy/)\nto avoid the device downloading a newer release straight away, if available.\nCheck also the Preloading and Preregistering section of the balena CLI's advanced\nmasterclass document:\nhttps://www.balena.io/docs/learn/more/masterclasses/advanced-cli/#5-preloading-and-preregistering\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).\n\nNote that the this command requires Docker to be installed, as further detailed\nin the balena CLI's installation instructions:\nhttps://github.com/balena-io/balena-cli/blob/master/INSTALL.md\nThe `--dockerHost` and `--dockerPort` flags allow a remote Docker engine to\nbe used, however the image file must be accessible to the remote Docker engine\non the same path given on the command line. This is because Docker's bind mount\nfeature is used to \"share\" the image with a container that performs the preload.",
+      "examples": [
+        "$ balena preload balena.img --fleet MyFleet --commit e1f2592fc6ee949e68756d4f4a48e49bff8d72a0",
+        "$ balena preload balena.img --fleet myorg/myfleet --splash-image image.png",
+        "$ balena preload balena.img"
+      ],
+      "flags": {
+        "fleet": {
+          "char": "f",
+          "description": "fleet name or slug (preferred)",
+          "name": "fleet",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "commit": {
+          "char": "c",
+          "description": "The commit hash of the release to preload. Use \"current\" to specify the current\nrelease (ignored if no appId is given). The current release is usually also the\nlatest, but can be pinned to a specific release. See:\nhttps://www.balena.io/docs/learn/deploy/release-strategy/release-policy/\nhttps://www.balena.io/docs/learn/more/masterclasses/fleet-management/#63-pin-using-the-api\nhttps://github.com/balena-io-examples/staged-releases",
+          "name": "commit",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "nolive": {
-          "description": "Don't run a live session on this push. The filesystem will not be monitored,\nand changes will not be synchronized to any running containers. Note that both\nthis flag and --detached are required to cause the process to end once the\ninitial build has completed.",
-          "name": "nolive",
+        "splash-image": {
+          "char": "s",
+          "description": "path to a png image to replace the splash screen",
+          "name": "splash-image",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "dont-check-arch": {
+          "description": "disable architecture compatibility check between image and fleet",
+          "name": "dont-check-arch",
           "allowNo": false,
           "type": "boolean"
         },
-        "detached": {
-          "char": "d",
-          "description": "When pushing to the cloud, this option will cause the build to start, then\nreturn execution back to the shell, with the status and release ID (if\napplicable).  When pushing to a local mode device, this option will cause\nthe command to not tail logs when the build has completed.",
-          "name": "detached",
-          "allowNo": false,
+        "pin-device-to-release": {
+          "char": "p",
+          "description": "pin the preloaded device to the preloaded release on provision",
+          "name": "pin-device-to-release",
+          "allowNo": true,
           "type": "boolean"
         },
-        "service": {
-          "description": "Reject logs not originating from this service.\nThis can be used in combination with --system and other --service flags.\nOnly valid when pushing to a local mode device.",
-          "name": "service",
+        "additional-space": {
+          "description": "expand the image by this amount of bytes instead of automatically estimating the required amount",
+          "name": "additional-space",
           "hasDynamicHelp": false,
-          "multiple": true,
+          "multiple": false,
           "type": "option"
         },
-        "system": {
-          "description": "Only show system logs. This can be used in combination with --service.\nOnly valid when pushing to a local mode device.",
-          "name": "system",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "env": {
-          "description": "When performing a push to device, run the built containers with environment\nvariables provided with this argument. Environment variables can be applied\nto individual services by adding their service name before the argument,\nseparated by a colon, e.g:\n\t--env main:MY_ENV=value\nNote that if the service name cannot be found in the composition, the entire\nleft hand side of the = character will be treated as the variable name.",
-          "name": "env",
+        "add-certificate": {
+          "description": "Add the given certificate (in PEM format) to /etc/ssl/certs in the preloading container.\nThe file name must end with '.crt' and must not be already contained in the preloader's\n/etc/ssl/certs folder.\nCan be repeated to add multiple certificates.",
+          "name": "add-certificate",
           "hasDynamicHelp": false,
           "multiple": true,
           "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"
+        "docker": {
+          "char": "P",
+          "description": "Path to a local docker socket (e.g. /var/run/docker.sock)",
+          "name": "docker",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         },
-        "multi-dockerignore": {
-          "char": "m",
-          "description": "Have each service use its own .dockerignore file. See \"balena help push\".",
-          "name": "multi-dockerignore",
-          "allowNo": false,
-          "type": "boolean"
+        "dockerHost": {
+          "char": "h",
+          "description": "Docker daemon hostname or IP address (dev machine or balena device) ",
+          "name": "dockerHost",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         },
-        "release-tag": {
-          "description": "Set release tags if the image build is successful (balenaCloud only). Multiple\narguments may be provided, alternating tag keys and values (see examples).\nHint: Empty values may be specified with \"\" (bash, cmd.exe) or '\"\"' (PowerShell).",
-          "exclusive": [
-            "detached"
-          ],
-          "name": "release-tag",
+        "dockerPort": {
+          "description": "Docker daemon TCP port number (hint: 2375 for balena devices)",
+          "name": "dockerPort",
           "hasDynamicHelp": false,
-          "multiple": true,
+          "multiple": false,
           "type": "option"
         },
-        "draft": {
-          "description": "Instruct the builder to create 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"
+        "ca": {
+          "description": "Docker host TLS certificate authority file",
+          "name": "ca",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         },
-        "note": {
-          "description": "The notes for this release",
-          "name": "note",
+        "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"
@@ -3966,18 +3965,19 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "push",
+      "id": "preload",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
+      "authenticated": true,
       "primary": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "push",
+        "preload",
         "index.js"
       ]
     },
@@ -4192,67 +4192,6 @@
         "index.js"
       ]
     },
-    "support": {
-      "aliases": [],
-      "args": {
-        "action": {
-          "description": "enable|disable support access",
-          "name": "action",
-          "options": [
-            "enable",
-            "disable"
-          ]
-        }
-      },
-      "description": "Grant or revoke support access for devices or fleets.\n\nGrant or revoke balena support agent access to devices or fleets\non balenaCloud. (This command does not apply to openBalena.)\nAccess will be automatically revoked once the specified duration has elapsed.\n\nDuration defaults to 24h, but can be specified using --duration flag in days\nor hours, e.g. '12h', '2d'.\n\nBoth --device and --fleet flags accept multiple values, specified as\na comma-separated list (with no spaces).\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).",
-      "examples": [
-        "balena support enable --device ab346f,cd457a --duration 3d",
-        "balena support enable --fleet myFleet --duration 12h",
-        "balena support disable -f myorg/myfleet"
-      ],
-      "flags": {
-        "device": {
-          "char": "d",
-          "description": "comma-separated list (no spaces) of device UUIDs",
-          "name": "device",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "fleet": {
-          "char": "f",
-          "description": "comma-separated list (no spaces) of fleet names or slugs (preferred)",
-          "name": "fleet",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "duration": {
-          "char": "t",
-          "description": "length of time to enable support for, in (h)ours or (d)ays, e.g. 12h, 2d",
-          "name": "duration",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "support",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "support",
-        "index.js"
-      ]
-    },
     "ssh-key:add": {
       "aliases": [
         "key add"
@@ -4401,26 +4340,65 @@
         "rm.js"
       ]
     },
-    "util:available-drives": {
+    "support": {
       "aliases": [],
-      "args": {},
-      "description": "List available drives.\n\nList available drives which are usable for writing an OS image to.\nDoes not list system drives.",
-      "flags": {},
+      "args": {
+        "action": {
+          "description": "enable|disable support access",
+          "name": "action",
+          "options": [
+            "enable",
+            "disable"
+          ]
+        }
+      },
+      "description": "Grant or revoke support access for devices or fleets.\n\nGrant or revoke balena support agent access to devices or fleets\non balenaCloud. (This command does not apply to openBalena.)\nAccess will be automatically revoked once the specified duration has elapsed.\n\nDuration defaults to 24h, but can be specified using --duration flag in days\nor hours, e.g. '12h', '2d'.\n\nBoth --device and --fleet flags accept multiple values, specified as\na comma-separated list (with no spaces).\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).",
+      "examples": [
+        "balena support enable --device ab346f,cd457a --duration 3d",
+        "balena support enable --fleet myFleet --duration 12h",
+        "balena support disable -f myorg/myfleet"
+      ],
+      "flags": {
+        "device": {
+          "char": "d",
+          "description": "comma-separated list (no spaces) of device UUIDs",
+          "name": "device",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "fleet": {
+          "char": "f",
+          "description": "comma-separated list (no spaces) of fleet names or slugs (preferred)",
+          "name": "fleet",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "duration": {
+          "char": "t",
+          "description": "length of time to enable support for, in (h)ours or (d)ays, e.g. 12h, 2d",
+          "name": "duration",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "util:available-drives",
+      "id": "support",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "offlineCompatible": true,
+      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "util",
-        "available-drives.js"
+        "support",
+        "index.js"
       ]
     },
     "tag:list": {
@@ -4646,6 +4624,28 @@
         "set.js"
       ]
     },
+    "util:available-drives": {
+      "aliases": [],
+      "args": {},
+      "description": "List available drives.\n\nList available drives which are usable for writing an OS image to.\nDoes not list system drives.",
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "util:available-drives",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "offlineCompatible": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "util",
+        "available-drives.js"
+      ]
+    },
     "version": {
       "aliases": [],
       "args": {},
@@ -4716,5 +4716,5 @@
       ]
     }
   },
-  "version": "22.2.0"
+  "version": "22.2.1"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "balena-cli",
-  "version": "22.2.0",
+  "version": "22.2.1",
   "description": "The official balena Command Line Interface",
   "main": "./build/app.js",
   "homepage": "https://github.com/balena-io/balena-cli",
@@ -255,6 +255,6 @@
     }
   },
   "versionist": {
-    "publishedAt": "2025-08-04T12:42:14.072Z"
+    "publishedAt": "2025-08-06T11:19:26.259Z"
   }
 }