balena-cli 23.2.15-build-update-compose-7-3-0-97bf26975807627a264274621ffcf8380aea838e-1 → 23.2.15-build-update-compose-tar-dependencies-132ab39d4a4a27c2766acc7a6aee1cedfbe13a2c-1

package/oclif.manifest.json

@@ -160,56 +160,6 @@
         "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": {
@@ -412,6 +362,56 @@
         "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": {},
@@ -1018,16 +1018,54 @@
         "list.js"
       ]
     },
-    "env:list": {
+    "device:deactivate": {
+      "aliases": [],
+      "args": {
+        "uuid": {
+          "description": "the UUID of the device to be deactivated",
+          "name": "uuid",
+          "required": true
+        }
+      },
+      "description": "Deactivate a device.\n\nDeactivate a device.\n\nNote this command asks for confirmation interactively.\nYou can avoid this by passing the `--yes` option.",
+      "examples": [
+        "$ balena device deactivate 7cf02a6",
+        "$ balena device deactivate 7cf02a6 --yes"
+      ],
+      "flags": {
+        "yes": {
+          "char": "y",
+          "description": "answer \"yes\" to all questions (non interactive use)",
+          "name": "yes",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "device:deactivate",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "device",
+        "deactivate.js"
+      ]
+    },
+    "device:detect": {
       "aliases": [],
       "args": {},
-      "description": "List the environment or config variables of a fleet, device or service.\n\nList the environment or configuration variables of a fleet, device or\nservice, as selected by the respective command-line options. (A service\ncorresponds to a Docker image/container in a microservices fleet.)\n\nThe results include fleet-wide (multiple devices), device-specific (multiple\nservices on a specific device) and service-specific variables that apply to the\nselected fleet, device or service. It can be thought of as including inherited\nvariables; for example, a service inherits device-wide variables, and a device\ninherits fleet-wide variables.\n\nThe printed output may include DEVICE and/or SERVICE columns to distinguish\nbetween fleet-wide, device-specific and service-specific variables.\nAn asterisk in these columns indicates that the variable applies to\n\"all devices\" or \"all services\".\n\nThe --config option is used to list \"configuration variables\" that control\nbalena platform features, as opposed to custom environment variables defined\nby the user. The --config and the --service options are mutually exclusive\nbecause configuration variables cannot be set for specific services.\n\nWhen --json is used, an empty JSON array ([]) is printed instead of an error \nmessage when no variables exist for the given query. When querying variables \nfor a device, note that the fleet name may be null in JSON output \n(or 'N/A' in tabular output) if the fleet that the device belonged to is no \nlonger accessible by the current user (for example, in case the current user \nwas removed from the fleet by the fleet's owner).\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).",
+      "description": "Scan for balenaOS devices on your local network.\n\nScan for balenaOS devices on your local network.\n\nThe output includes device information collected through balenaEngine for\ndevices running a development image of balenaOS. Devices running a production\nimage do not expose balenaEngine (on TCP port 2375), which is why less\ninformation is printed about them.",
       "examples": [
-        "$ balena env list --fleet myorg/myfleet",
-        "$ balena env list --fleet MyFleet --service MyService",
-        "$ balena env list --fleet MyFleet --config",
-        "$ balena env list --device 7cf02a6",
-        "$ balena env list --device 7cf02a6 --service MyService"
+        "$ balena device detect",
+        "$ balena device detect --timeout 120",
+        "$ balena device detect --verbose"
       ],
       "flags": {
         "json": {
@@ -1037,45 +1075,17 @@
           "allowNo": false,
           "type": "boolean"
         },
-        "fleet": {
-          "char": "f",
-          "description": "fleet name or slug (preferred)",
-          "exclusive": [
-            "device"
-          ],
-          "name": "fleet",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "config": {
-          "char": "c",
-          "description": "show configuration variables only",
-          "exclusive": [
-            "service"
-          ],
-          "name": "config",
+        "verbose": {
+          "char": "v",
+          "description": "display full info",
+          "name": "verbose",
           "allowNo": false,
           "type": "boolean"
         },
-        "device": {
-          "char": "d",
-          "description": "device UUID",
-          "exclusive": [
-            "fleet"
-          ],
-          "name": "device",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "service": {
-          "char": "s",
-          "description": "service name",
-          "exclusive": [
-            "config"
-          ],
-          "name": "service",
+        "timeout": {
+          "char": "t",
+          "description": "scan timeout in seconds",
+          "name": "timeout",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -1083,255 +1093,191 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "env:list",
+      "id": "device:detect",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": true,
+      "primary": true,
+      "root": true,
+      "offlineCompatible": true,
+      "dockerInfoProperties": [
+        "Containers",
+        "ContainersRunning",
+        "ContainersPaused",
+        "ContainersStopped",
+        "Images",
+        "Driver",
+        "SystemTime",
+        "KernelVersion",
+        "OperatingSystem",
+        "Architecture"
+      ],
+      "dockerVersionProperties": [
+        "Version",
+        "ApiVersion"
+      ],
+      "noDevicesFoundMessage": "Could not find any balenaOS devices on the local network.",
+      "windowsTipMessage": "\n\nNote for Windows users:\n  The 'device detect' command relies on the Bonjour service. Check whether Bonjour is\n  installed (Control Panel > Programs and Features). If not, you can download\n  Bonjour for Windows (included with Bonjour Print Services) from here:\n  https://support.apple.com/kb/DL999\n\n  After installing Bonjour, restart your PC and run the 'balena device detect' command\n  again.",
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "env",
-        "list.js"
+        "device",
+        "detect.js"
       ]
     },
-    "env:rename": {
+    "device:identify": {
       "aliases": [],
       "args": {
-        "id": {
-          "description": "variable's numeric database ID",
-          "name": "id",
-          "required": true
-        },
-        "value": {
-          "description": "variable value; if omitted, use value from this process' environment",
-          "name": "value",
+        "uuid": {
+          "description": "the uuid of the device to identify",
+          "name": "uuid",
           "required": true
         }
       },
-      "description": "Change the value of a config or env var for a fleet, device or service.\n\nChange the value of a configuration or environment variable for a fleet,\ndevice or service, as selected by command-line options.\n\nVariables are selected by their database ID (as reported by the 'balena env list'\ncommand) and one of six database \"resource types\":\n\n- fleet environment variable\n- fleet configuration variable (--config)\n- fleet service variable (--service)\n- device environment variable (--device)\n- device configuration variable (--device --config)\n- device service variable (--device --service)\n\nThe --device option selects a device-specific variable instead of a fleet\nvariable.\n\nThe --config option selects a configuration variable. Configuration variable\nnames typically start with the 'BALENA_' or 'RESIN_' prefixes and are used to\nconfigure balena platform features.\n\nThe --service option selects a service variable, which is an environment variable\nthat applies to a specifc service (container) in a microservices (multicontainer)\nfleet.\n\nThe --service and --config options cannot be used together, but they can be\nused alongside the --device option to select a device-specific service or\nconfiguration variable.",
+      "description": "Identify a device.\n\nIdentify a device by making the ACT LED blink (Raspberry Pi).",
       "examples": [
-        "$ balena env rename 123123 emacs",
-        "$ balena env rename 234234 emacs --service",
-        "$ balena env rename 345345 emacs --device",
-        "$ balena env rename 456456 emacs --device --service",
-        "$ balena env rename 567567 1 --config",
-        "$ balena env rename 678678 1 --device --config"
+        "$ balena device identify 23c73a1"
       ],
-      "flags": {
-        "config": {
-          "char": "c",
-          "description": "select a configuration variable (may be used together with the --device option)",
-          "exclusive": [
-            "service"
-          ],
-          "name": "config",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "device": {
-          "char": "d",
-          "description": "select a device-specific variable instead of a fleet variable",
-          "name": "device",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "service": {
-          "char": "s",
-          "description": "select a service variable (may be used together with the --device option)",
-          "exclusive": [
-            "config"
-          ],
-          "name": "service",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
+      "flags": {},
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "env:rename",
+      "id": "device:identify",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
+      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "env",
-        "rename.js"
+        "device",
+        "identify.js"
       ]
     },
-    "env:rm": {
+    "device": {
       "aliases": [],
       "args": {
-        "id": {
-          "description": "variable's numeric database ID",
-          "name": "id",
+        "uuid": {
+          "description": "the device uuid",
+          "name": "uuid",
           "required": true
         }
       },
-      "description": "Remove a config or env var from a fleet, device or service.\n\nRemove a configuration or environment variable from a fleet, device\nor service, as selected by command-line options.\n\nVariables are selected by their database ID (as reported by the 'balena env list'\ncommand) and one of six database \"resource types\":\n\n- fleet environment variable\n- fleet configuration variable (--config)\n- fleet service variable (--service)\n- device environment variable (--device)\n- device configuration variable (--device --config)\n- device service variable (--device --service)\n\nThe --device option selects a device-specific variable instead of a fleet\nvariable.\n\nThe --config option selects a configuration variable. Configuration variable\nnames typically start with the 'BALENA_' or 'RESIN_' prefixes and are used to\nconfigure balena platform features.\n\nThe --service option selects a service variable, which is an environment variable\nthat applies to a specifc service (container) in a microservices (multicontainer)\nfleet.\n\nThe --service and --config options cannot be used together, but they can be\nused alongside the --device option to select a device-specific service or\nconfiguration variable.\n\nInteractive confirmation is normally asked before the variable is deleted.\nThe --yes option disables this behavior.",
+      "description": "Show info about a single device.\n\nShow information about a single device.",
       "examples": [
-        "$ balena env rm 123123",
-        "$ balena env rm 234234 --yes",
-        "$ balena env rm 345345 --config",
-        "$ balena env rm 456456 --service",
-        "$ balena env rm 567567 --device",
-        "$ balena env rm 678678 --device --config",
-        "$ balena env rm 789789 --device --service --yes"
+        "$ balena device 7cf02a6",
+        "$ balena device 7cf02a6 --view"
       ],
       "flags": {
-        "config": {
-          "char": "c",
-          "description": "select a configuration variable (may be used together with the --device option)",
-          "exclusive": [
-            "service"
-          ],
-          "name": "config",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "device": {
-          "char": "d",
-          "description": "select a device-specific variable instead of a fleet variable",
-          "name": "device",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "service": {
-          "char": "s",
-          "description": "select a service variable (may be used together with the --device option)",
-          "exclusive": [
-            "config"
-          ],
-          "name": "service",
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
           "allowNo": false,
           "type": "boolean"
         },
-        "yes": {
-          "char": "y",
-          "description": "do not prompt for confirmation before deleting the variable",
-          "name": "yes",
+        "view": {
+          "description": "open device dashboard page",
+          "name": "view",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "env:rm",
+      "id": "device",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
-      "enableJsonFlag": false,
+      "enableJsonFlag": true,
+      "authenticated": true,
+      "primary": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "env",
-        "rm.js"
+        "device",
+        "index.js"
       ]
     },
-    "env:set": {
+    "device:init": {
       "aliases": [],
-      "args": {
-        "name": {
-          "description": "environment or config variable name",
-          "name": "name",
-          "required": true
-        },
-        "value": {
-          "description": "variable value; if omitted, use value from this process' environment",
-          "name": "value",
-          "required": false
-        }
-      },
-      "description": "Add or update env or config variable to fleets, devices or services.\n\nAdd or update an environment or config variable to one or more fleets, devices or\nservices, as selected by the respective command-line options. Either the\n--fleet or the --device option must be provided,  and either may be be\nused alongside the --service option to define a service-specific variable.\n(A service corresponds to a Docker image/container in a microservices fleet.)\nWhen the --service option is used in conjunction with the --device option,\nthe service variable applies to the selected device only.  Otherwise, it\napplies to all devices of the selected fleet. If the --service option is\nomitted, the variable applies to all services.\n\nIf VALUE is omitted, the CLI will attempt to use the value of the environment\nvariable of same name in the CLI process' environment. In this case, a warning\nmessage will be printed. Use `--quiet` to suppress it.\n\n'BALENA_' or 'RESIN_' are reserved variable name prefixes used to identify\n\"configuration variables\". Configuration variables control balena platform\nfeatures and are treated specially by balenaOS and the balena supervisor\nrunning on devices. They are also stored differently in the balenaCloud API\ndatabase. Configuration variables cannot be set for specific services,\ntherefore the --service option cannot be used when the variable name starts\nwith a reserved prefix. When defining custom fleet variables, please avoid\nthese reserved prefixes.\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).",
+      "args": {},
+      "description": "Initialize a device with balenaOS.\n\nRegister a new device in the selected fleet, download the OS image for the\nfleet's default device type, configure the image and write it to an SD card.\nThis command effectively combines several other balena CLI commands in one,\nnamely:\n\n'balena device register'\n'balena os download'\n'balena config generate'\n'balena os configure'\n'balena os local flash'\n\nPossible arguments for the '--fleet', '--os-version' and '--drive' options can\nbe listed respectively with the commands:\n\n'balena fleet list'\n'balena os versions'\n'balena util available-drives'\n\nIf the '--fleet' or '--drive' options are omitted, interactive menus will be\npresented with values to choose from. If the '--os-version' option is omitted,\nthe latest released OS version for the fleet's default device type will be used.\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\nImage configuration questions will be asked interactively unless a pre-configured\n'config.json' file is provided with the '--config' option.  The file can be\ngenerated with the 'balena config generate' command.",
       "examples": [
-        "$ balena env set TERM --fleet MyFleet",
-        "$ balena env set EDITOR vim -f myorg/myfleet",
-        "$ balena env set EDITOR vim --fleet MyFleet,MyFleet2",
-        "$ balena env set EDITOR vim --fleet MyFleet --service MyService",
-        "$ balena env set EDITOR vim --fleet MyFleet,MyFleet2 --service MyService,MyService2",
-        "$ balena env set EDITOR vim --device 7cf02a6",
-        "$ balena env set EDITOR vim --device 7cf02a6,d6f1433",
-        "$ balena env set EDITOR vim --device 7cf02a6 --service MyService",
-        "$ balena env set EDITOR vim --device 7cf02a6,d6f1433 --service MyService,MyService2"
+        "$ balena device init",
+        "$ balena device init -f myorg/myfleet",
+        "$ balena device init --fleet myFleet --os-version 2.101.7 --drive /dev/disk5",
+        "$ balena device init --fleet myFleet --os-version 2.83.21+rev1.prod --drive /dev/disk5",
+        "$ balena device init --config config.json --os-version 2.101.7 --drive /dev/disk5 --yes"
       ],
       "flags": {
         "fleet": {
           "char": "f",
           "description": "fleet name or slug (preferred)",
           "exclusive": [
-            "device"
+            "config"
           ],
           "name": "fleet",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "device": {
-          "char": "d",
-          "description": "device UUID",
+        "config": {
+          "description": "path to the config JSON file, see `balena config generate`",
           "exclusive": [
-            "fleet"
+            "fleet",
+            "advanced",
+            "provisioning-key-name",
+            "provisioning-key-expiry-date"
           ],
-          "name": "device",
+          "name": "config",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "quiet": {
-          "char": "q",
-          "description": "suppress warning messages",
-          "name": "quiet",
+        "os-version": {
+          "description": "exact version number, or a valid semver range,\nor 'latest' (includes pre-releases),\nor 'default' (excludes pre-releases if at least one stable version is available),\nor 'recommended' (excludes pre-releases, will fail if only pre-release versions are available),\nor 'menu' (will show the interactive menu)",
+          "name": "os-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "advanced": {
+          "char": "v",
+          "description": "show advanced configuration options",
+          "name": "advanced",
           "allowNo": false,
           "type": "boolean"
         },
-        "service": {
-          "char": "s",
-          "description": "service name",
-          "name": "service",
+        "provisioning-key-name": {
+          "description": "custom key name assigned to generated provisioning api key",
+          "name": "provisioning-key-name",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "env:set",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": false,
-      "enableJsonFlag": false,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "env",
-        "set.js"
-      ]
-    },
-    "device:deactivate": {
-      "aliases": [],
-      "args": {
-        "uuid": {
-          "description": "the UUID of the device to be deactivated",
-          "name": "uuid",
-          "required": true
-        }
-      },
-      "description": "Deactivate a device.\n\nDeactivate a device.\n\nNote this command asks for confirmation interactively.\nYou can avoid this by passing the `--yes` option.",
-      "examples": [
-        "$ balena device deactivate 7cf02a6",
-        "$ balena device deactivate 7cf02a6 --yes"
-      ],
-      "flags": {
+        },
+        "provisioning-key-expiry-date": {
+          "description": "expiry date assigned to generated provisioning api key (format: YYYY-MM-DD)",
+          "name": "provisioning-key-expiry-date",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "drive": {
+          "char": "d",
+          "description": "the drive to write the image to, eg. `/dev/sdb` or `/dev/mmcblk0`.\nCareful with this as you can erase your hard drive.\nCheck `balena util available-drives` for available options.",
+          "name": "drive",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
         "yes": {
           "char": "y",
           "description": "answer \"yes\" to all questions (non interactive use)",
@@ -1342,7 +1288,7 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "device:deactivate",
+      "id": "device:init",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -1354,17 +1300,17 @@
         "build",
         "commands",
         "device",
-        "deactivate.js"
+        "init.js"
       ]
     },
-    "device:detect": {
+    "device:list": {
       "aliases": [],
       "args": {},
-      "description": "Scan for balenaOS devices on your local network.\n\nScan for balenaOS devices on your local network.\n\nThe output includes device information collected through balenaEngine for\ndevices running a development image of balenaOS. Devices running a production\nimage do not expose balenaEngine (on TCP port 2375), which is why less\ninformation is printed about them.",
+      "description": "List all devices.\n\nList all of your devices.\n\nDevices can be filtered by fleet with the `--fleet` option.\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 device detect",
-        "$ balena device detect --timeout 120",
-        "$ balena device detect --verbose"
+        "$ balena device list",
+        "$ balena device list --fleet MyFleet",
+        "$ balena device list -f myorg/myfleet"
       ],
       "flags": {
         "json": {
@@ -1374,17 +1320,10 @@
           "allowNo": false,
           "type": "boolean"
         },
-        "verbose": {
-          "char": "v",
-          "description": "display full info",
-          "name": "verbose",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "timeout": {
-          "char": "t",
-          "description": "scan timeout in seconds",
-          "name": "timeout",
+        "fleet": {
+          "char": "f",
+          "description": "fleet name or slug (preferred)",
+          "name": "fleet",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -1392,245 +1331,7 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "device:detect",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": true,
-      "primary": true,
-      "root": true,
-      "offlineCompatible": true,
-      "dockerInfoProperties": [
-        "Containers",
-        "ContainersRunning",
-        "ContainersPaused",
-        "ContainersStopped",
-        "Images",
-        "Driver",
-        "SystemTime",
-        "KernelVersion",
-        "OperatingSystem",
-        "Architecture"
-      ],
-      "dockerVersionProperties": [
-        "Version",
-        "ApiVersion"
-      ],
-      "noDevicesFoundMessage": "Could not find any balenaOS devices on the local network.",
-      "windowsTipMessage": "\n\nNote for Windows users:\n  The 'device detect' command relies on the Bonjour service. Check whether Bonjour is\n  installed (Control Panel > Programs and Features). If not, you can download\n  Bonjour for Windows (included with Bonjour Print Services) from here:\n  https://support.apple.com/kb/DL999\n\n  After installing Bonjour, restart your PC and run the 'balena device detect' command\n  again.",
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "device",
-        "detect.js"
-      ]
-    },
-    "device:identify": {
-      "aliases": [],
-      "args": {
-        "uuid": {
-          "description": "the uuid of the device to identify",
-          "name": "uuid",
-          "required": true
-        }
-      },
-      "description": "Identify a device.\n\nIdentify a device by making the ACT LED blink (Raspberry Pi).",
-      "examples": [
-        "$ balena device identify 23c73a1"
-      ],
-      "flags": {},
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "device:identify",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "device",
-        "identify.js"
-      ]
-    },
-    "device": {
-      "aliases": [],
-      "args": {
-        "uuid": {
-          "description": "the device uuid",
-          "name": "uuid",
-          "required": true
-        }
-      },
-      "description": "Show info about a single device.\n\nShow information about a single device.",
-      "examples": [
-        "$ balena device 7cf02a6",
-        "$ balena device 7cf02a6 --view"
-      ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "view": {
-          "description": "open device dashboard page",
-          "name": "view",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "device",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": true,
-      "authenticated": true,
-      "primary": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "device",
-        "index.js"
-      ]
-    },
-    "device:init": {
-      "aliases": [],
-      "args": {},
-      "description": "Initialize a device with balenaOS.\n\nRegister a new device in the selected fleet, download the OS image for the\nfleet's default device type, configure the image and write it to an SD card.\nThis command effectively combines several other balena CLI commands in one,\nnamely:\n\n'balena device register'\n'balena os download'\n'balena config generate'\n'balena os configure'\n'balena os local flash'\n\nPossible arguments for the '--fleet', '--os-version' and '--drive' options can\nbe listed respectively with the commands:\n\n'balena fleet list'\n'balena os versions'\n'balena util available-drives'\n\nIf the '--fleet' or '--drive' options are omitted, interactive menus will be\npresented with values to choose from. If the '--os-version' option is omitted,\nthe latest released OS version for the fleet's default device type will be used.\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\nImage configuration questions will be asked interactively unless a pre-configured\n'config.json' file is provided with the '--config' option.  The file can be\ngenerated with the 'balena config generate' command.",
-      "examples": [
-        "$ balena device init",
-        "$ balena device init -f myorg/myfleet",
-        "$ balena device init --fleet myFleet --os-version 2.101.7 --drive /dev/disk5",
-        "$ balena device init --fleet myFleet --os-version 2.83.21+rev1.prod --drive /dev/disk5",
-        "$ balena device init --config config.json --os-version 2.101.7 --drive /dev/disk5 --yes"
-      ],
-      "flags": {
-        "fleet": {
-          "char": "f",
-          "description": "fleet name or slug (preferred)",
-          "exclusive": [
-            "config"
-          ],
-          "name": "fleet",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "config": {
-          "description": "path to the config JSON file, see `balena config generate`",
-          "exclusive": [
-            "fleet",
-            "advanced",
-            "provisioning-key-name",
-            "provisioning-key-expiry-date"
-          ],
-          "name": "config",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "os-version": {
-          "description": "exact version number, or a valid semver range,\nor 'latest' (includes pre-releases),\nor 'default' (excludes pre-releases if at least one stable version is available),\nor 'recommended' (excludes pre-releases, will fail if only pre-release versions are available),\nor 'menu' (will show the interactive menu)",
-          "name": "os-version",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "advanced": {
-          "char": "v",
-          "description": "show advanced configuration options",
-          "name": "advanced",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "provisioning-key-name": {
-          "description": "custom key name assigned to generated provisioning api key",
-          "name": "provisioning-key-name",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "provisioning-key-expiry-date": {
-          "description": "expiry date assigned to generated provisioning api key (format: YYYY-MM-DD)",
-          "name": "provisioning-key-expiry-date",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "drive": {
-          "char": "d",
-          "description": "the drive to write the image to, eg. `/dev/sdb` or `/dev/mmcblk0`.\nCareful with this as you can erase your hard drive.\nCheck `balena util available-drives` for available options.",
-          "name": "drive",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "yes": {
-          "char": "y",
-          "description": "answer \"yes\" to all questions (non interactive use)",
-          "name": "yes",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "device:init",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "device",
-        "init.js"
-      ]
-    },
-    "device:list": {
-      "aliases": [],
-      "args": {},
-      "description": "List all devices.\n\nList all of your devices.\n\nDevices can be filtered by fleet with the `--fleet` option.\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 device list",
-        "$ balena device list --fleet MyFleet",
-        "$ balena device list -f myorg/myfleet"
-      ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "fleet": {
-          "char": "f",
-          "description": "fleet name or slug (preferred)",
-          "name": "fleet",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "device:list",
+      "id": "device:list",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -2494,47 +2195,346 @@
       },
       "description": "Tunnel local ports to your balenaOS device.\n\nUse this command to open local TCP ports that tunnel to listening sockets in a\nbalenaOS device.\n\nFor example, this command could be used to expose the ssh server of a balenaOS\ndevice (port number 22222) on the local machine, or to expose a web server\nrunning on the device. The port numbers do not have be the same between the\ndevice and the local machine, and multiple ports may be tunneled in a single\ncommand line.\n\nPort mappings are specified in the format: <remotePort>[:[localIP:]localPort]\nlocalIP defaults to 'localhost', and localPort defaults to the specified\nremotePort value.\n\nNote: the -p (--port) flag must be provided at the end of the command line,\nas per examples.\n\nIn the case of openBalena, the tunnel command in CLI v12.38.5 or later requires\nopenBalena v3.1.2 or later. Older CLI versions work with older openBalena\nversions.",
       "examples": [
-        "# map remote port 22222 to localhost:22222",
-        "$ balena device tunnel myFleet -p 22222",
-        "",
-        "# map remote port 22222 to localhost:222",
-        "$ balena device tunnel 2ead211 -p 22222:222",
-        "",
-        "# map remote port 22222 to any address on your host machine, port 22222",
-        "$ balena device tunnel 1546690 -p 22222:0.0.0.0",
-        "",
-        "# map remote port 22222 to any address on your host machine, port 222",
-        "$ balena device tunnel myFleet -p 22222:0.0.0.0:222",
-        "",
-        "# multiple port tunnels can be specified at any one time",
-        "$ balena device tunnel myFleet -p 8080:3000 -p 8081:9000"
+        "# map remote port 22222 to localhost:22222",
+        "$ balena device tunnel myFleet -p 22222",
+        "",
+        "# map remote port 22222 to localhost:222",
+        "$ balena device tunnel 2ead211 -p 22222:222",
+        "",
+        "# map remote port 22222 to any address on your host machine, port 22222",
+        "$ balena device tunnel 1546690 -p 22222:0.0.0.0",
+        "",
+        "# map remote port 22222 to any address on your host machine, port 222",
+        "$ balena device tunnel myFleet -p 22222:0.0.0.0:222",
+        "",
+        "# multiple port tunnels can be specified at any one time",
+        "$ balena device tunnel myFleet -p 8080:3000 -p 8081:9000"
+      ],
+      "flags": {
+        "port": {
+          "char": "p",
+          "description": "port mapping in the format <remotePort>[:[localIP:]localPort]",
+          "name": "port",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "device:tunnel",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "primary": true,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "device",
+        "tunnel.js"
+      ]
+    },
+    "env:list": {
+      "aliases": [],
+      "args": {},
+      "description": "List the environment or config variables of a fleet, device or service.\n\nList the environment or configuration variables of a fleet, device or\nservice, as selected by the respective command-line options. (A service\ncorresponds to a Docker image/container in a microservices fleet.)\n\nThe results include fleet-wide (multiple devices), device-specific (multiple\nservices on a specific device) and service-specific variables that apply to the\nselected fleet, device or service. It can be thought of as including inherited\nvariables; for example, a service inherits device-wide variables, and a device\ninherits fleet-wide variables.\n\nThe printed output may include DEVICE and/or SERVICE columns to distinguish\nbetween fleet-wide, device-specific and service-specific variables.\nAn asterisk in these columns indicates that the variable applies to\n\"all devices\" or \"all services\".\n\nThe --config option is used to list \"configuration variables\" that control\nbalena platform features, as opposed to custom environment variables defined\nby the user. The --config and the --service options are mutually exclusive\nbecause configuration variables cannot be set for specific services.\n\nWhen --json is used, an empty JSON array ([]) is printed instead of an error \nmessage when no variables exist for the given query. When querying variables \nfor a device, note that the fleet name may be null in JSON output \n(or 'N/A' in tabular output) if the fleet that the device belonged to is no \nlonger accessible by the current user (for example, in case the current user \nwas removed from the fleet by the fleet's owner).\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 env list --fleet myorg/myfleet",
+        "$ balena env list --fleet MyFleet --service MyService",
+        "$ balena env list --fleet MyFleet --config",
+        "$ balena env list --device 7cf02a6",
+        "$ balena env list --device 7cf02a6 --service MyService"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "fleet": {
+          "char": "f",
+          "description": "fleet name or slug (preferred)",
+          "exclusive": [
+            "device"
+          ],
+          "name": "fleet",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "config": {
+          "char": "c",
+          "description": "show configuration variables only",
+          "exclusive": [
+            "service"
+          ],
+          "name": "config",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "device": {
+          "char": "d",
+          "description": "device UUID",
+          "exclusive": [
+            "fleet"
+          ],
+          "name": "device",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "service": {
+          "char": "s",
+          "description": "service name",
+          "exclusive": [
+            "config"
+          ],
+          "name": "service",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "env:list",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "env",
+        "list.js"
+      ]
+    },
+    "env:rename": {
+      "aliases": [],
+      "args": {
+        "id": {
+          "description": "variable's numeric database ID",
+          "name": "id",
+          "required": true
+        },
+        "value": {
+          "description": "variable value; if omitted, use value from this process' environment",
+          "name": "value",
+          "required": true
+        }
+      },
+      "description": "Change the value of a config or env var for a fleet, device or service.\n\nChange the value of a configuration or environment variable for a fleet,\ndevice or service, as selected by command-line options.\n\nVariables are selected by their database ID (as reported by the 'balena env list'\ncommand) and one of six database \"resource types\":\n\n- fleet environment variable\n- fleet configuration variable (--config)\n- fleet service variable (--service)\n- device environment variable (--device)\n- device configuration variable (--device --config)\n- device service variable (--device --service)\n\nThe --device option selects a device-specific variable instead of a fleet\nvariable.\n\nThe --config option selects a configuration variable. Configuration variable\nnames typically start with the 'BALENA_' or 'RESIN_' prefixes and are used to\nconfigure balena platform features.\n\nThe --service option selects a service variable, which is an environment variable\nthat applies to a specifc service (container) in a microservices (multicontainer)\nfleet.\n\nThe --service and --config options cannot be used together, but they can be\nused alongside the --device option to select a device-specific service or\nconfiguration variable.",
+      "examples": [
+        "$ balena env rename 123123 emacs",
+        "$ balena env rename 234234 emacs --service",
+        "$ balena env rename 345345 emacs --device",
+        "$ balena env rename 456456 emacs --device --service",
+        "$ balena env rename 567567 1 --config",
+        "$ balena env rename 678678 1 --device --config"
+      ],
+      "flags": {
+        "config": {
+          "char": "c",
+          "description": "select a configuration variable (may be used together with the --device option)",
+          "exclusive": [
+            "service"
+          ],
+          "name": "config",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "device": {
+          "char": "d",
+          "description": "select a device-specific variable instead of a fleet variable",
+          "name": "device",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "service": {
+          "char": "s",
+          "description": "select a service variable (may be used together with the --device option)",
+          "exclusive": [
+            "config"
+          ],
+          "name": "service",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "env:rename",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "env",
+        "rename.js"
+      ]
+    },
+    "env:rm": {
+      "aliases": [],
+      "args": {
+        "id": {
+          "description": "variable's numeric database ID",
+          "name": "id",
+          "required": true
+        }
+      },
+      "description": "Remove a config or env var from a fleet, device or service.\n\nRemove a configuration or environment variable from a fleet, device\nor service, as selected by command-line options.\n\nVariables are selected by their database ID (as reported by the 'balena env list'\ncommand) and one of six database \"resource types\":\n\n- fleet environment variable\n- fleet configuration variable (--config)\n- fleet service variable (--service)\n- device environment variable (--device)\n- device configuration variable (--device --config)\n- device service variable (--device --service)\n\nThe --device option selects a device-specific variable instead of a fleet\nvariable.\n\nThe --config option selects a configuration variable. Configuration variable\nnames typically start with the 'BALENA_' or 'RESIN_' prefixes and are used to\nconfigure balena platform features.\n\nThe --service option selects a service variable, which is an environment variable\nthat applies to a specifc service (container) in a microservices (multicontainer)\nfleet.\n\nThe --service and --config options cannot be used together, but they can be\nused alongside the --device option to select a device-specific service or\nconfiguration variable.\n\nInteractive confirmation is normally asked before the variable is deleted.\nThe --yes option disables this behavior.",
+      "examples": [
+        "$ balena env rm 123123",
+        "$ balena env rm 234234 --yes",
+        "$ balena env rm 345345 --config",
+        "$ balena env rm 456456 --service",
+        "$ balena env rm 567567 --device",
+        "$ balena env rm 678678 --device --config",
+        "$ balena env rm 789789 --device --service --yes"
+      ],
+      "flags": {
+        "config": {
+          "char": "c",
+          "description": "select a configuration variable (may be used together with the --device option)",
+          "exclusive": [
+            "service"
+          ],
+          "name": "config",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "device": {
+          "char": "d",
+          "description": "select a device-specific variable instead of a fleet variable",
+          "name": "device",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "service": {
+          "char": "s",
+          "description": "select a service variable (may be used together with the --device option)",
+          "exclusive": [
+            "config"
+          ],
+          "name": "service",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "yes": {
+          "char": "y",
+          "description": "do not prompt for confirmation before deleting the variable",
+          "name": "yes",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "env:rm",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "env",
+        "rm.js"
+      ]
+    },
+    "env:set": {
+      "aliases": [],
+      "args": {
+        "name": {
+          "description": "environment or config variable name",
+          "name": "name",
+          "required": true
+        },
+        "value": {
+          "description": "variable value; if omitted, use value from this process' environment",
+          "name": "value",
+          "required": false
+        }
+      },
+      "description": "Add or update env or config variable to fleets, devices or services.\n\nAdd or update an environment or config variable to one or more fleets, devices or\nservices, as selected by the respective command-line options. Either the\n--fleet or the --device option must be provided,  and either may be be\nused alongside the --service option to define a service-specific variable.\n(A service corresponds to a Docker image/container in a microservices fleet.)\nWhen the --service option is used in conjunction with the --device option,\nthe service variable applies to the selected device only.  Otherwise, it\napplies to all devices of the selected fleet. If the --service option is\nomitted, the variable applies to all services.\n\nIf VALUE is omitted, the CLI will attempt to use the value of the environment\nvariable of same name in the CLI process' environment. In this case, a warning\nmessage will be printed. Use `--quiet` to suppress it.\n\n'BALENA_' or 'RESIN_' are reserved variable name prefixes used to identify\n\"configuration variables\". Configuration variables control balena platform\nfeatures and are treated specially by balenaOS and the balena supervisor\nrunning on devices. They are also stored differently in the balenaCloud API\ndatabase. Configuration variables cannot be set for specific services,\ntherefore the --service option cannot be used when the variable name starts\nwith a reserved prefix. When defining custom fleet variables, please avoid\nthese reserved prefixes.\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 env set TERM --fleet MyFleet",
+        "$ balena env set EDITOR vim -f myorg/myfleet",
+        "$ balena env set EDITOR vim --fleet MyFleet,MyFleet2",
+        "$ balena env set EDITOR vim --fleet MyFleet --service MyService",
+        "$ balena env set EDITOR vim --fleet MyFleet,MyFleet2 --service MyService,MyService2",
+        "$ balena env set EDITOR vim --device 7cf02a6",
+        "$ balena env set EDITOR vim --device 7cf02a6,d6f1433",
+        "$ balena env set EDITOR vim --device 7cf02a6 --service MyService",
+        "$ balena env set EDITOR vim --device 7cf02a6,d6f1433 --service MyService,MyService2"
       ],
       "flags": {
-        "port": {
-          "char": "p",
-          "description": "port mapping in the format <remotePort>[:[localIP:]localPort]",
-          "name": "port",
+        "fleet": {
+          "char": "f",
+          "description": "fleet name or slug (preferred)",
+          "exclusive": [
+            "device"
+          ],
+          "name": "fleet",
           "hasDynamicHelp": false,
-          "multiple": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "device": {
+          "char": "d",
+          "description": "device UUID",
+          "exclusive": [
+            "fleet"
+          ],
+          "name": "device",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "quiet": {
+          "char": "q",
+          "description": "suppress warning messages",
+          "name": "quiet",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "service": {
+          "char": "s",
+          "description": "service name",
+          "name": "service",
+          "hasDynamicHelp": false,
+          "multiple": false,
           "type": "option"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "device:tunnel",
+      "id": "env:set",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
-      "strict": true,
+      "strict": false,
       "enableJsonFlag": false,
-      "primary": true,
-      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "device",
-        "tunnel.js"
+        "env",
+        "set.js"
       ]
     },
     "fleet:create": {
@@ -3148,116 +3148,246 @@
           "multiple": false,
           "type": "option"
         },
-        "user": {
-          "char": "u",
-          "dependsOn": [
-            "credentials"
-          ],
-          "exclusive": [
-            "email"
-          ],
-          "hidden": true,
-          "name": "user",
+        "user": {
+          "char": "u",
+          "dependsOn": [
+            "credentials"
+          ],
+          "exclusive": [
+            "email"
+          ],
+          "hidden": true,
+          "name": "user",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "password": {
+          "char": "p",
+          "dependsOn": [
+            "credentials"
+          ],
+          "description": "password",
+          "name": "password",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "port": {
+          "char": "P",
+          "dependsOn": [
+            "web"
+          ],
+          "description": "TCP port number of local HTTP login server (--web auth only)",
+          "name": "port",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "hideExperimentalWarning": {
+          "char": "H",
+          "description": "Hides warning for experimental features",
+          "name": "hideExperimentalWarning",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "login",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "primary": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "login",
+        "index.js"
+      ]
+    },
+    "logout": {
+      "aliases": [],
+      "args": {},
+      "description": "Logout from balena.\n\nLogout from your balena account.",
+      "examples": [
+        "$ balena logout"
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "logout",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "logout",
+        "index.js"
+      ]
+    },
+    "organization:list": {
+      "aliases": [],
+      "args": {},
+      "description": "List all organizations.\n\nlist all the organizations that you are a member of.",
+      "examples": [
+        "$ balena organization list"
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "organization:list",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "organization",
+        "list.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"
         },
-        "password": {
-          "char": "p",
-          "dependsOn": [
-            "credentials"
-          ],
-          "description": "password",
-          "name": "password",
+        "dockerPort": {
+          "description": "Docker daemon TCP port number (hint: 2375 for balena devices)",
+          "name": "dockerPort",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "port": {
-          "char": "P",
-          "dependsOn": [
-            "web"
-          ],
-          "description": "TCP port number of local HTTP login server (--web auth only)",
-          "name": "port",
+        "ca": {
+          "description": "Docker host TLS certificate authority file",
+          "name": "ca",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "hideExperimentalWarning": {
-          "char": "H",
-          "description": "Hides warning for experimental features",
-          "name": "hideExperimentalWarning",
-          "allowNo": false,
-          "type": "boolean"
+        "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": "login",
+      "id": "preload",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
+      "authenticated": true,
       "primary": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "login",
-        "index.js"
-      ]
-    },
-    "logout": {
-      "aliases": [],
-      "args": {},
-      "description": "Logout from balena.\n\nLogout from your balena account.",
-      "examples": [
-        "$ balena logout"
-      ],
-      "flags": {},
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "logout",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "logout",
+        "preload",
         "index.js"
       ]
     },
-    "organization:list": {
-      "aliases": [],
-      "args": {},
-      "description": "List all organizations.\n\nlist all the organizations that you are a member of.",
-      "examples": [
-        "$ balena organization list"
-      ],
-      "flags": {},
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "organization:list",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "organization",
-        "list.js"
-      ]
-    },
     "os:configure": {
       "aliases": [],
       "args": {
@@ -3552,179 +3682,49 @@
         "commands",
         "os",
         "initialize.js"
-      ]
-    },
-    "os:versions": {
-      "aliases": [],
-      "args": {
-        "type": {
-          "description": "device type",
-          "name": "type",
-          "required": true
-        }
-      },
-      "description": "Show available balenaOS versions for the given device type.\n\nShow the available balenaOS versions for the given device type.\nCheck available types with `balena device-type list`.\n\nbalenaOS ESR versions can be listed with the '--esr' option. See also:\nhttps://www.balena.io/docs/reference/OS/extended-support-release/",
-      "examples": [
-        "$ balena os versions raspberrypi3"
-      ],
-      "flags": {
-        "esr": {
-          "description": "select balenaOS ESR versions",
-          "name": "esr",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "include-draft": {
-          "description": "include pre-release balenaOS versions",
-          "name": "include-draft",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "os:versions",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "os",
-        "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"
+      ]
+    },
+    "os:versions": {
+      "aliases": [],
+      "args": {
+        "type": {
+          "description": "device type",
+          "name": "type",
+          "required": true
+        }
+      },
+      "description": "Show available balenaOS versions for the given device type.\n\nShow the available balenaOS versions for the given device type.\nCheck available types with `balena device-type list`.\n\nbalenaOS ESR versions can be listed with the '--esr' option. See also:\nhttps://www.balena.io/docs/reference/OS/extended-support-release/",
+      "examples": [
+        "$ balena os versions raspberrypi3"
+      ],
+      "flags": {
+        "esr": {
+          "description": "select balenaOS ESR versions",
+          "name": "esr",
+          "allowNo": false,
+          "type": "boolean"
         },
-        "key": {
-          "description": "Docker host TLS key file",
-          "name": "key",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
+        "include-draft": {
+          "description": "include pre-release balenaOS versions",
+          "name": "include-draft",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "preload",
+      "id": "os:versions",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "authenticated": true,
-      "primary": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "preload",
-        "index.js"
+        "os",
+        "versions.js"
       ]
     },
     "push": {
@@ -3892,41 +3892,24 @@
         "index.js"
       ]
     },
-    "release-asset:delete": {
+    "release:finalize": {
       "aliases": [],
       "args": {
         "commitOrId": {
-          "description": "the commit or ID of the release",
+          "description": "the commit or ID of the release to finalize",
           "name": "commitOrId",
           "required": true
         }
       },
-      "description": "Delete a release asset.\n\nDelete a release asset with the specified key. This action cannot be undone.",
+      "description": "Finalize a release.\n\nFinalize a release. Releases can be \"draft\" or \"final\", and this command\nchanges a draft release into a final release. Draft releases can be created\nwith the `--draft` option of the `balena build` or `balena deploy`\ncommands.\n\nDraft releases are not automatically deployed to devices tracking the latest\nrelease. For a draft release to be deployed to a device, the device should be\nexplicity pinned to that release. Conversely, final releases may trigger immediate\ndeployment to unpinned devices (subject to a device's  polling period) and, for\nthis reason, final releases cannot be changed back to draft status.",
       "examples": [
-        "$ balena release-asset delete 1234567 --key config.json",
-        "$ balena release-asset delete a777f7345fe3d655c1c981aa642e5555 --key app.tar.gz",
-        "$ balena release-asset delete 1234567 --key old-asset --yes"
+        "$ balena release finalize a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release finalize 1234567"
       ],
-      "flags": {
-        "key": {
-          "description": "the key of the release asset to delete",
-          "name": "key",
-          "required": true,
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "yes": {
-          "char": "y",
-          "description": "skip confirmation prompt",
-          "name": "yes",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
+      "flags": {},
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release-asset:delete",
+      "id": "release:finalize",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -3937,80 +3920,101 @@
       "relativePath": [
         "build",
         "commands",
-        "release-asset",
-        "delete.js"
+        "release",
+        "finalize.js"
       ]
     },
-    "release-asset:download": {
+    "release": {
       "aliases": [],
       "args": {
         "commitOrId": {
-          "description": "the commit or ID of the release",
+          "description": "the commit or ID of the release to get information",
           "name": "commitOrId",
           "required": true
         }
       },
-      "description": "Download a release asset.\n\nDownload a release asset with the specified key. By default, the file will be saved\nwith the original filename. Use the --output flag to specify a different output path.\n\nIf the output file already exists, the command will prompt for confirmation before\noverwriting, unless the --overwrite flag is specified.",
+      "description": "Get info for a release.",
       "examples": [
-        "$ balena release-asset download 1234567 --key config.json",
-        "$ balena release-asset download a777f7345fe3d655c1c981aa642e5555 --key app.tar.gz --output ./downloads/app.tar.gz",
-        "$ balena release-asset download 1234567 --key large-file.bin -o output.bin",
-        "$ balena release-asset download 1234567 --key config.json --overwrite"
+        "$ balena release a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release 1234567"
       ],
       "flags": {
-        "key": {
-          "description": "the key of the release asset to download",
-          "name": "key",
-          "required": true,
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "output": {
-          "char": "o",
-          "description": "output path for the downloaded file",
-          "name": "output",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
         },
-        "overwrite": {
-          "description": "overwrite existing file without confirmation",
-          "name": "overwrite",
+        "composition": {
+          "char": "c",
+          "description": "Return the release composition",
+          "name": "composition",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release-asset:download",
+      "id": "release",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
-      "enableJsonFlag": false,
+      "enableJsonFlag": true,
       "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "release-asset",
-        "download.js"
+        "release",
+        "index.js"
       ]
     },
-    "release-asset:list": {
+    "release:invalidate": {
       "aliases": [],
       "args": {
         "commitOrId": {
-          "description": "the commit or ID of the release",
+          "description": "the commit or ID of the release to invalidate",
           "name": "commitOrId",
           "required": true
         }
       },
-      "description": "List all release assets.\n\nList all assets for a specific release.",
+      "description": "Invalidate a release.\n\nInvalidate a release.\n\nInvalid releases are not automatically deployed to devices tracking the latest\nrelease. For an invalid release to be deployed to a device, the device should be\nexplicity pinned to that release.",
       "examples": [
-        "$ balena release-asset list 1234567",
-        "$ balena release-asset list a777f7345fe3d655c1c981aa642e5555"
+        "$ balena release invalidate a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release invalidate 1234567"
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "release:invalidate",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "release",
+        "invalidate.js"
+      ]
+    },
+    "release:list": {
+      "aliases": [],
+      "args": {
+        "fleet": {
+          "description": "fleet name or slug (preferred)",
+          "name": "fleet",
+          "required": true
+        }
+      },
+      "description": "List all releases of a fleet.\n\nList all releases of the given fleet.\n\nFleets may be specified by fleet name or slug. Slugs are recommended because\nthey are unique and unambiguous. Slugs can be listed with the `balena fleet list`\ncommand. Note that slugs may change if the fleet is renamed. Fleet names are\nnot unique and may result in \"Fleet is ambiguous\" errors at any time (even if\n\"it used to work in the past\"), for example if the name clashes with a newly\ncreated public/open fleet, or with fleets from other balena accounts that you\nmay be invited to join under any role.  For this reason, fleet names are\nespecially discouraged in scripts (e.g. CI environments).",
+      "examples": [
+        "$ balena release list myorg/myfleet"
       ],
       "flags": {
         "json": {
@@ -4023,7 +4027,7 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release-asset:list",
+      "id": "release:list",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -4034,65 +4038,28 @@
       "relativePath": [
         "build",
         "commands",
-        "release-asset",
+        "release",
         "list.js"
       ]
     },
-    "release-asset:upload": {
+    "release:validate": {
       "aliases": [],
       "args": {
         "commitOrId": {
-          "description": "the commit or ID of the release",
+          "description": "the commit or ID of the release to validate",
           "name": "commitOrId",
           "required": true
-        },
-        "filePath": {
-          "description": "path to the file to upload",
-          "name": "filePath",
-          "required": true
         }
       },
-      "description": "Upload a release asset.\n\nUpload a file as a release asset with the specified key. If the asset already exists,\nyou can use the --overwrite flag to replace it. You can customize the upload behavior with\n--chunk-size and --parallel-chunks options for larger files.",
+      "description": "Validate a release.\n\nValidate a release.\n\nValid releases are automatically deployed to devices tracking the latest\nrelease if they are finalized.",
       "examples": [
-        "$ balena release-asset upload 1234567 ./path/to/config.json --key config.json",
-        "$ balena release-asset upload a777f7345fe3d655c1c981aa642e5555 ./app.tar.gz --key app.tar.gz --overwrite",
-        "$ balena release-asset upload 1234567 ./file.bin --key large-file.bin --chunk-size 10485760 --parallel-chunks 10"
+        "$ balena release validate a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release validate 1234567"
       ],
-      "flags": {
-        "key": {
-          "description": "the key for the release asset",
-          "name": "key",
-          "required": true,
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "overwrite": {
-          "description": "overwrite the asset if it already exists",
-          "name": "overwrite",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "chunk-size": {
-          "description": "chunk size in bytes for multipart upload (minimum 5MB)",
-          "name": "chunk-size",
-          "default": 5242880,
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "parallel-chunks": {
-          "description": "number of chunks to upload in parallel",
-          "name": "parallel-chunks",
-          "default": 5,
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
+      "flags": {},
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release-asset:upload",
+      "id": "release:validate",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -4103,107 +4070,126 @@
       "relativePath": [
         "build",
         "commands",
-        "release-asset",
-        "upload.js"
+        "release",
+        "validate.js"
       ]
     },
-    "release:finalize": {
+    "settings": {
       "aliases": [],
-      "args": {
-        "commitOrId": {
-          "description": "the commit or ID of the release to finalize",
-          "name": "commitOrId",
-          "required": true
-        }
-      },
-      "description": "Finalize a release.\n\nFinalize a release. Releases can be \"draft\" or \"final\", and this command\nchanges a draft release into a final release. Draft releases can be created\nwith the `--draft` option of the `balena build` or `balena deploy`\ncommands.\n\nDraft releases are not automatically deployed to devices tracking the latest\nrelease. For a draft release to be deployed to a device, the device should be\nexplicity pinned to that release. Conversely, final releases may trigger immediate\ndeployment to unpinned devices (subject to a device's  polling period) and, for\nthis reason, final releases cannot be changed back to draft status.",
+      "args": {},
+      "description": "Print current settings.\n\nUse this command to display the current balena CLI settings.",
       "examples": [
-        "$ balena release finalize a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release finalize 1234567"
+        "$ balena settings"
       ],
       "flags": {},
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release:finalize",
+      "id": "settings",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "release",
-        "finalize.js"
+        "settings",
+        "index.js"
       ]
     },
-    "release": {
+    "release-asset:delete": {
       "aliases": [],
       "args": {
         "commitOrId": {
-          "description": "the commit or ID of the release to get information",
+          "description": "the commit or ID of the release",
           "name": "commitOrId",
           "required": true
         }
       },
-      "description": "Get info for a release.",
+      "description": "Delete a release asset.\n\nDelete a release asset with the specified key. This action cannot be undone.",
       "examples": [
-        "$ balena release a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release 1234567"
+        "$ balena release-asset delete 1234567 --key config.json",
+        "$ balena release-asset delete a777f7345fe3d655c1c981aa642e5555 --key app.tar.gz",
+        "$ balena release-asset delete 1234567 --key old-asset --yes"
       ],
       "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
+        "key": {
+          "description": "the key of the release asset to delete",
+          "name": "key",
+          "required": true,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         },
-        "composition": {
-          "char": "c",
-          "description": "Return the release composition",
-          "name": "composition",
+        "yes": {
+          "char": "y",
+          "description": "skip confirmation prompt",
+          "name": "yes",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release",
+      "id": "release-asset:delete",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
-      "enableJsonFlag": true,
+      "enableJsonFlag": false,
       "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "release",
-        "index.js"
+        "release-asset",
+        "delete.js"
       ]
     },
-    "release:invalidate": {
+    "release-asset:download": {
       "aliases": [],
       "args": {
         "commitOrId": {
-          "description": "the commit or ID of the release to invalidate",
+          "description": "the commit or ID of the release",
           "name": "commitOrId",
           "required": true
         }
       },
-      "description": "Invalidate a release.\n\nInvalidate a release.\n\nInvalid releases are not automatically deployed to devices tracking the latest\nrelease. For an invalid release to be deployed to a device, the device should be\nexplicity pinned to that release.",
+      "description": "Download a release asset.\n\nDownload a release asset with the specified key. By default, the file will be saved\nwith the original filename. Use the --output flag to specify a different output path.\n\nIf the output file already exists, the command will prompt for confirmation before\noverwriting, unless the --overwrite flag is specified.",
       "examples": [
-        "$ balena release invalidate a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release invalidate 1234567"
+        "$ balena release-asset download 1234567 --key config.json",
+        "$ balena release-asset download a777f7345fe3d655c1c981aa642e5555 --key app.tar.gz --output ./downloads/app.tar.gz",
+        "$ balena release-asset download 1234567 --key large-file.bin -o output.bin",
+        "$ balena release-asset download 1234567 --key config.json --overwrite"
       ],
-      "flags": {},
+      "flags": {
+        "key": {
+          "description": "the key of the release asset to download",
+          "name": "key",
+          "required": true,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "output": {
+          "char": "o",
+          "description": "output path for the downloaded file",
+          "name": "output",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "overwrite": {
+          "description": "overwrite existing file without confirmation",
+          "name": "overwrite",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release:invalidate",
+      "id": "release-asset:download",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -4214,22 +4200,23 @@
       "relativePath": [
         "build",
         "commands",
-        "release",
-        "invalidate.js"
+        "release-asset",
+        "download.js"
       ]
     },
-    "release:list": {
+    "release-asset:list": {
       "aliases": [],
       "args": {
-        "fleet": {
-          "description": "fleet name or slug (preferred)",
-          "name": "fleet",
+        "commitOrId": {
+          "description": "the commit or ID of the release",
+          "name": "commitOrId",
           "required": true
         }
       },
-      "description": "List all releases of a fleet.\n\nList all releases of the given fleet.\n\nFleets may be specified by fleet name or slug. Slugs are recommended because\nthey are unique and unambiguous. Slugs can be listed with the `balena fleet list`\ncommand. Note that slugs may change if the fleet is renamed. Fleet names are\nnot unique and may result in \"Fleet is ambiguous\" errors at any time (even if\n\"it used to work in the past\"), for example if the name clashes with a newly\ncreated public/open fleet, or with fleets from other balena accounts that you\nmay be invited to join under any role.  For this reason, fleet names are\nespecially discouraged in scripts (e.g. CI environments).",
+      "description": "List all release assets.\n\nList all assets for a specific release.",
       "examples": [
-        "$ balena release list myorg/myfleet"
+        "$ balena release-asset list 1234567",
+        "$ balena release-asset list a777f7345fe3d655c1c981aa642e5555"
       ],
       "flags": {
         "json": {
@@ -4242,7 +4229,7 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release:list",
+      "id": "release-asset:list",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -4253,28 +4240,65 @@
       "relativePath": [
         "build",
         "commands",
-        "release",
+        "release-asset",
         "list.js"
       ]
     },
-    "release:validate": {
+    "release-asset:upload": {
       "aliases": [],
       "args": {
         "commitOrId": {
-          "description": "the commit or ID of the release to validate",
+          "description": "the commit or ID of the release",
           "name": "commitOrId",
           "required": true
+        },
+        "filePath": {
+          "description": "path to the file to upload",
+          "name": "filePath",
+          "required": true
         }
       },
-      "description": "Validate a release.\n\nValidate a release.\n\nValid releases are automatically deployed to devices tracking the latest\nrelease if they are finalized.",
+      "description": "Upload a release asset.\n\nUpload a file as a release asset with the specified key. If the asset already exists,\nyou can use the --overwrite flag to replace it. You can customize the upload behavior with\n--chunk-size and --parallel-chunks options for larger files.",
       "examples": [
-        "$ balena release validate a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release validate 1234567"
+        "$ balena release-asset upload 1234567 ./path/to/config.json --key config.json",
+        "$ balena release-asset upload a777f7345fe3d655c1c981aa642e5555 ./app.tar.gz --key app.tar.gz --overwrite",
+        "$ balena release-asset upload 1234567 ./file.bin --key large-file.bin --chunk-size 10485760 --parallel-chunks 10"
       ],
-      "flags": {},
+      "flags": {
+        "key": {
+          "description": "the key for the release asset",
+          "name": "key",
+          "required": true,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "overwrite": {
+          "description": "overwrite the asset if it already exists",
+          "name": "overwrite",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "chunk-size": {
+          "description": "chunk size in bytes for multipart upload (minimum 5MB)",
+          "name": "chunk-size",
+          "default": 5242880,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "parallel-chunks": {
+          "description": "number of chunks to upload in parallel",
+          "name": "parallel-chunks",
+          "default": 5,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release:validate",
+      "id": "release-asset:upload",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -4285,31 +4309,68 @@
       "relativePath": [
         "build",
         "commands",
-        "release",
-        "validate.js"
+        "release-asset",
+        "upload.js"
       ]
     },
-    "settings": {
+    "support": {
       "aliases": [],
-      "args": {},
-      "description": "Print current settings.\n\nUse this command to display the current balena CLI settings.",
+      "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 settings"
+        "balena support enable --device ab346f,cd457a --duration 3d",
+        "balena support enable --fleet myFleet --duration 12h",
+        "balena support disable -f myorg/myfleet"
       ],
-      "flags": {},
+      "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": "settings",
+      "id": "support",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
+      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "settings",
+        "support",
         "index.js"
       ]
     },
@@ -4448,67 +4509,6 @@
         "rm.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"
-      ]
-    },
     "tag:list": {
       "aliases": [],
       "args": {},