balena-cli 25.1.2 → 25.1.3

package/oclif.manifest.json

@@ -3365,651 +3365,483 @@
         "rm.js"
       ]
     },
-    "os:configure": {
+    "preload": {
       "aliases": [],
       "args": {
         "image": {
-          "description": "path to a balenaOS image file, e.g. \"rpi3.img\"",
+          "description": "the image file path",
           "name": "image",
           "required": true
         }
       },
-      "description": "Configure a previously downloaded balenaOS image.\n\nConfigure a previously downloaded balenaOS image for a specific device type\nor fleet.\n\nConfiguration settings such as WiFi authentication will be taken from the\nfollowing sources, in precedence order:\n1. Command-line options like `--config-wifi-ssid`\n2. A given `config.json` file specified with the `--config` option.\n3. User input through interactive prompts (text menus).\n\nThe --device-type option is used to override the fleet's default device type,\nin case of a fleet with mixed device types.\n\nThe '--dev' option is used to configure balenaOS to operate in development mode,\nallowing unauthenticated root ssh access and exposing network ports such as\nbalenaEngine's 2375 (unencrypted). This option causes `\"developmentMode\": true`\nto be inserted in the 'config.json' file in the image's boot partition. Development\nmode (as a configurable option) is applicable to balenaOS releases from early\n2022. Older releases have separate development and production balenaOS images\nthat cannot be reconfigured through 'config.json' or the '--dev' option. Do not\nconfuse the balenaOS \"development mode\" with a device's \"local mode\", the latter\nbeing a supervisor feature that allows the \"balena push\" command to push a user's\napplication directly to a device in the local network.\n\nThe '--secureBoot' option is used to configure a balenaOS installer image to opt-in\nsecure boot and disk encryption.\n\nThe --system-connection (-c) option is used to inject NetworkManager connection\nprofiles for additional network interfaces, such as cellular/GSM or additional\nWiFi or ethernet connections. This option may be passed multiple times in case there\nare multiple files to inject. See connection profile examples and reference at:\nhttps://www.balena.io/docs/reference/OS/network/2.x/\nhttps://developer.gnome.org/NetworkManager/stable/ref-settings.html\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": "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 os configure ../path/rpi3.img --device 7cf02a6",
-        "$ balena os configure ../path/rpi3.img --fleet myorg/myfleet",
-        "$ balena os configure ../path/rpi3.img -f myorg/myfleet --device-type raspberrypi3",
-        "$ balena os configure ../path/rpi3.img --config myWifiConfig.json"
+        "$ 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)",
-          "exclusive": [
-            "device",
-            "config"
-          ],
           "name": "fleet",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "device": {
-          "char": "d",
-          "description": "device UUID",
-          "exclusive": [
-            "fleet",
-            "device-type",
-            "config",
-            "provisioning-key-name",
-            "provisioning-key-expiry-date"
-          ],
-          "name": "device",
+        "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"
         },
-        "config": {
-          "description": "path to a pre-generated config.json file to be injected in the OS image",
-          "exclusive": [
-            "fleet",
-            "device",
-            "advanced",
-            "config-app-update-poll-interval",
-            "config-network",
-            "config-wifi-key",
-            "config-wifi-ssid",
-            "dev",
-            "secureBoot",
-            "device-type",
-            "initial-device-name",
-            "provisioning-key-name",
-            "provisioning-key-expiry-date"
-          ],
-          "name": "config",
+        "splash-image": {
+          "char": "s",
+          "description": "path to a png image to replace the splash screen",
+          "name": "splash-image",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "advanced": {
-          "char": "v",
-          "description": "ask advanced configuration questions (when in interactive mode)",
-          "name": "advanced",
+        "dont-check-arch": {
+          "description": "disable architecture compatibility check between image and fleet",
+          "name": "dont-check-arch",
           "allowNo": false,
           "type": "boolean"
         },
-        "config-app-update-poll-interval": {
-          "description": "supervisor cloud polling interval in minutes (e.g. for variable updates)",
-          "name": "config-app-update-poll-interval",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
+        "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"
         },
-        "config-network": {
-          "description": "device network type (non-interactive configuration)",
-          "name": "config-network",
+        "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,
-          "options": [
-            "ethernet",
-            "wifi"
-          ],
           "type": "option"
         },
-        "config-wifi-key": {
-          "description": "WiFi key (password) (non-interactive configuration)",
-          "name": "config-wifi-key",
+        "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": false,
+          "multiple": true,
           "type": "option"
         },
-        "config-wifi-ssid": {
-          "description": "WiFi SSID (network name) (non-interactive configuration)",
-          "name": "config-wifi-ssid",
+        "docker": {
+          "char": "P",
+          "description": "Path to a local docker socket (e.g. /var/run/docker.sock)",
+          "name": "docker",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "dev": {
-          "description": "Configure balenaOS to operate in development mode",
-          "name": "dev",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "secureBoot": {
-          "description": "Configure balenaOS installer to opt-in secure boot and disk encryption",
-          "name": "secureBoot",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "device-type": {
-          "dependsOn": [
-            "fleet"
-          ],
-          "description": "device type slug (e.g. \"raspberrypi3\") to override the fleet device type",
-          "name": "device-type",
+        "dockerHost": {
+          "char": "h",
+          "description": "Docker daemon hostname or IP address (dev machine or balena device) ",
+          "name": "dockerHost",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "initial-device-name": {
-          "description": "This option will set the device name when the device provisions",
-          "name": "initial-device-name",
+        "dockerPort": {
+          "description": "Docker daemon TCP port number (hint: 2375 for balena devices)",
+          "name": "dockerPort",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "provisioning-key-name": {
-          "description": "custom key name assigned to generated provisioning api key",
-          "exclusive": [
-            "config",
-            "device"
-          ],
-          "name": "provisioning-key-name",
+        "ca": {
+          "description": "Docker host TLS certificate authority file",
+          "name": "ca",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "provisioning-key-expiry-date": {
-          "description": "expiry date assigned to generated provisioning api key (format: YYYY-MM-DD)",
-          "exclusive": [
-            "config",
-            "device"
-          ],
-          "name": "provisioning-key-expiry-date",
+        "cert": {
+          "description": "Docker host TLS certificate file",
+          "name": "cert",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "system-connection": {
-          "char": "c",
-          "description": "paths to local files to place into the 'system-connections' directory",
-          "name": "system-connection",
-          "required": false,
+        "key": {
+          "description": "Docker host TLS key file",
+          "name": "key",
           "hasDynamicHelp": false,
-          "multiple": true,
+          "multiple": false,
           "type": "option"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "os:configure",
+      "id": "preload",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
       "authenticated": true,
+      "primary": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "os",
-        "configure.js"
+        "preload",
+        "index.js"
       ]
     },
-    "os:download": {
+    "push": {
       "aliases": [],
       "args": {
-        "type": {
-          "description": "the device type",
-          "name": "type",
+        "fleetOrDevice": {
+          "description": "fleet name or slug, or local device IP address or \".local\" hostname",
+          "name": "fleetOrDevice",
           "required": true
         }
       },
-      "description": "Download an unconfigured OS image.\n\nDownload an unconfigured OS image for the specified device type.\nCheck available device types with 'balena device-type list'.\n\nNote: Currently this command only works with balenaCloud, not openBalena.\nIf using openBalena, please download the OS from: https://www.balena.io/os/\n\nThe '--version' option is used to select the balenaOS version. If omitted,\nthe latest released version is downloaded (and if only pre-release versions\nexist, the latest pre-release version is downloaded).\n\nUse '--type' to specify the type of OS download\nIf omitted, the default type for the specified device type-version combination is used.\nSome OS download types may not be available for certain device types and versions.\n\nUse '--version menu' or '--version menu-esr' to interactively select the\nOS version. The latter lists ESR versions which are only available for\ndownload on Production and Enterprise plans. See also:\nhttps://www.balena.io/docs/reference/OS/extended-support-release/\n\nDevelopment images can be selected by appending `.dev` to the version.",
+      "description": "Build release images on balenaCloud servers or on a local mode device.\n\nBuild release images on balenaCloud servers or on a local mode device.\n\nWhen building on the balenaCloud servers, the given source directory will be\nsent to the remote server. This can be used as a drop-in replacement for the\n\"git push\" deployment method.\n\nWhen building on a local mode device, the given source directory will be\nbuilt on the device, and the resulting containers will be run on the device.\nLogs will be streamed back from the device as part of the same invocation.\nThe web dashboard can be used to switch a device to local mode:\nhttps://www.balena.io/docs/learn/develop/local-mode/\nNote that local mode requires a supervisor version of at least v7.21.0.\nThe logs from only a single service can be shown with the --service flag, and\nshowing only the system logs can be achieved with --system. Note that these\nflags can be used together.\n\nWhen pushing to a local device a live session will be started.\nThe project source folder is watched for filesystem events, and changes\nto files and folders are automatically synchronized to the running\ncontainers. The synchronization is only in one direction, from this machine to\nthe device, and changes made on the device itself may be overwritten.\nThis feature requires a device running supervisor version v9.7.0 or greater.\n\nREGISTRY SECRETS  \nThe --registry-secrets option specifies a JSON or YAML file containing private\nDocker registry usernames and passwords to be used when pulling base images.\nSample registry-secrets YAML file:\n```\n\t'my-registry-server.com:25000':\n\t\tusername: ann\n\t\tpassword: hunter2\n\t'':  # Use the empty string to refer to the Docker Hub\n\t\tusername: mike\n\t\tpassword: cze14\n\t'eu.gcr.io':  # Google Container Registry\n\t\tusername: '_json_key'\n\t\tpassword: '{escaped contents of the GCR keyfile.json file}'\n```\nFor a sample project using registry secrets with the Google Container Registry,\ncheck: https://github.com/balena-io-examples/sample-gcr-registry-secrets\n\nIf the --registry-secrets option is not specified, and a secrets.yml or\nsecrets.json file exists in the balena directory (usually $HOME/.balena),\nthis file will be used instead.\n\nDOCKERIGNORE AND GITIGNORE FILES  \nBy default, the balena CLI will use a single \".dockerignore\" file (if any) at\nthe project root (--source directory) in order to decide which source files to\nexclude from the \"build context\" (tar stream) sent to balenaCloud, Docker\ndaemon or balenaEngine.  In a microservices (multicontainer) fleet, the\nsource directory is the directory that contains the \"docker-compose.yml\" file.\n\nThe --multi-dockerignore (-m) option may be used with microservices\n(multicontainer) fleets that define a docker-compose.yml file. When this\noption is used, each service subdirectory (defined by the `build` or\n`build.context` service properties in the docker-compose.yml file) is\nfiltered separately according to a .dockerignore file defined in the service\nsubdirectory. If no .dockerignore file exists in a service subdirectory, then\nonly the default .dockerignore patterns (see below) apply for that service\nsubdirectory.\n\nWhen the --multi-dockerignore (-m) option is used, the .dockerignore file (if\nany) defined at the overall project root will be used to filter files and\nsubdirectories other than service subdirectories. It will not have any effect\non service subdirectories, whether or not a service subdirectory defines its\nown .dockerignore file. Multiple .dockerignore files are not merged or added\ntogether, and cannot override or extend other files. This behavior maximizes\ncompatibility with the standard docker-compose tool, while still allowing a\nroot .dockerignore file (at the overall project root) to filter files and\nfolders that are outside service subdirectories.\n\nbalena CLI v11 also took .gitignore files into account. This behavior was\ndeprecated in CLI v12 and removed in CLI v13. Please use .dockerignore files\ninstead.\n\nDefault .dockerignore patterns  \nA few default/hardcoded dockerignore patterns are \"merged\" (in memory) with the\npatterns found in the applicable .dockerignore files, in the following order:\n```\n    **/.git\n    < user's patterns from the applicable '.dockerignore' file, if any >\n    !**/.balena\n    !**/.resin\n    !**/Dockerfile\n    !**/Dockerfile.*\n    !**/docker-compose.yml\n```\nThese patterns always apply, whether or not .dockerignore files exist in the\nproject. If necessary, the effect of the `**/.git` pattern may be modified by\nadding exception patterns to the applicable .dockerignore file(s), for example\n`!mysubmodule/.git`. For documentation on pattern format, see:\n- https://docs.docker.com/engine/reference/builder/#dockerignore-file\n- https://www.npmjs.com/package/@balena/dockerignore\n\nNote: the --service and --env flags must come after the fleetOrDevice\nparameter, as per examples.",
       "examples": [
-        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img",
-        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2.101.7",
-        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2022.7.0",
-        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version ^2.90.0",
-        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2.60.1+rev1",
-        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2.60.1+rev1.dev",
-        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2021.10.2.prod",
-        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version latest",
-        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version menu",
-        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version menu-esr",
-        "$ balena os download generic-amd64 -o ../foo/bar/generic-amd64.img --type installation-media"
+        "$ balena push myFleet",
+        "$ balena push myFleet --source <source directory>",
+        "$ balena push myFleet -s <source directory>",
+        "$ balena push myFleet --source <source directory> --note \"this is the note for this release\"",
+        "$ balena push myFleet --release-tag key1 \"\" key2 \"value2 with spaces\"",
+        "$ balena push myorg/myfleet",
+        "",
+        "$ balena push 10.0.0.1",
+        "$ balena push 10.0.0.1 --source <source directory>",
+        "$ balena push 10.0.0.1 --service my-service",
+        "$ balena push 10.0.0.1 --env MY_ENV_VAR=value --env my-service:SERVICE_VAR=value",
+        "$ balena push 10.0.0.1 --nolive",
+        "",
+        "$ balena push 23c73a1.local --system",
+        "$ balena push 23c73a1.local --system --service my-service"
       ],
       "flags": {
-        "output": {
-          "char": "o",
-          "description": "output path",
-          "name": "output",
-          "required": true,
+        "source": {
+          "char": "s",
+          "description": "Source directory to be sent to balenaCloud or balenaOS device\n(default: current working dir)",
+          "name": "source",
+          "default": ".",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "version": {
-          "description": "version number (ESR or non-ESR versions),\nor semver range (non-ESR versions only),\nor 'latest' (excludes invalidated & pre-releases),\nor 'menu' (interactive menu, non-ESR versions),\nor 'menu-esr' (interactive menu, ESR versions)",
-          "name": "version",
+        "emulated": {
+          "char": "e",
+          "description": "Don't use the faster, native balenaCloud ARM builders; force slower QEMU ARM\nemulation on Intel x86-64 builders. This flag is sometimes used to investigate\nsuspected issues with the balenaCloud backend.",
+          "name": "emulated",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "dockerfile": {
+          "description": "Alternative Dockerfile name/path, relative to the source folder",
+          "name": "dockerfile",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "type": {
-          "description": "'disk-image' (for flashing onto device system disk/storage)\nor 'installation-media' (for creating installation media to automatically erase, format, and install balenaOS on a device)",
-          "name": "type",
+        "nocache": {
+          "char": "c",
+          "description": "Don't use cached layers of previously built images for this project. This\nensures that the latest base image and packages are pulled. Note that build\nlogs may still display the message _\"Pulling previous images for caching\npurposes\" (as the cloud builder needs previous images to compute delta\nupdates), but the logs will not display the \"Using cache\" lines for each\nbuild step of a Dockerfile.",
+          "name": "nocache",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "pull": {
+          "description": "When pushing to a local device, force the base images to be pulled again.\nCurrently this option is ignored when pushing to the balenaCloud builders.",
+          "name": "pull",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "noparent-check": {
+          "description": "Disable project validation check of 'docker-compose.yml' file in parent folder",
+          "name": "noparent-check",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "registry-secrets": {
+          "char": "R",
+          "description": "Path to a local YAML or JSON file containing Docker registry passwords used\nto pull base images. Note that if registry-secrets are not provided on the\ncommand line, a secrets configuration file from the balena directory will be\nused (usually $HOME/.balena/secrets.yml|.json)",
+          "name": "registry-secrets",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "installation-media",
-            "disk-image"
-          ],
           "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "os:download",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "os",
-        "download.js"
-      ]
-    },
-    "os:initialize": {
-      "aliases": [],
-      "args": {
-        "image": {
-          "description": "path to OS image",
-          "name": "image",
-          "required": true
-        }
-      },
-      "description": "Initialize an os image for a device.\n\n\t\tInitialize an os image for a device with a previously\n\t\tconfigured operating system image and flash the\n\t\tan external storage drive or the device's storage\n\t\tmedium depending on the device type.\n\t\t\n\nNote: Initializing the device may ask for administrative permissions\nbecause we need to access the raw devices directly.",
-      "examples": [
-        "$ balena os initialize ../path/rpi.img --type raspberry-pi"
-      ],
-      "flags": {
-        "type": {
-          "char": "t",
-          "description": "device type (Check available types with `balena device-type list`)",
-          "name": "type",
-          "required": true,
+        },
+        "nolive": {
+          "description": "Don't run a live session on this push. The filesystem will not be monitored,\nand changes will not be synchronized to any running containers. Note that both\nthis flag and --detached are required to cause the process to end once the\ninitial build has completed.",
+          "name": "nolive",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "detached": {
+          "char": "d",
+          "description": "When pushing to the cloud, this option will cause the build to start, then\nreturn execution back to the shell, with the status and release ID (if\napplicable).  When pushing to a local mode device, this option will cause\nthe command to not tail logs when the build has completed.",
+          "name": "detached",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "service": {
+          "description": "Reject logs not originating from this service.\nThis can be used in combination with --system and other --service flags.\nOnly valid when pushing to a local mode device.",
+          "name": "service",
           "hasDynamicHelp": false,
-          "multiple": false,
+          "multiple": true,
           "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",
+        "system": {
+          "description": "Only show system logs. This can be used in combination with --service.\nOnly valid when pushing to a local mode device.",
+          "name": "system",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "env": {
+          "description": "When performing a push to device, run the built containers with environment\nvariables provided with this argument. Environment variables can be applied\nto individual services by adding their service name before the argument,\nseparated by a colon, e.g:\n\t--env main:MY_ENV=value\nNote that if the service name cannot be found in the composition, the entire\nleft hand side of the = character will be treated as the variable name.",
+          "name": "env",
           "hasDynamicHelp": false,
-          "multiple": false,
+          "multiple": true,
           "type": "option"
         },
-        "yes": {
-          "char": "y",
-          "description": "answer \"yes\" to all questions (non interactive use)",
-          "name": "yes",
+        "noconvert-eol": {
+          "description": "Don't convert line endings from CRLF (Windows format) to LF (Unix format).",
+          "name": "noconvert-eol",
           "allowNo": false,
           "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "os:initialize",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "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",
+        },
+        "multi-dockerignore": {
+          "char": "m",
+          "description": "Have each service use its own .dockerignore file. See \"balena help push\".",
+          "name": "multi-dockerignore",
           "allowNo": false,
           "type": "boolean"
         },
-        "include-draft": {
-          "description": "include pre-release balenaOS versions",
-          "name": "include-draft",
+        "release-tag": {
+          "description": "Set release tags if the image build is successful (balenaCloud only). Multiple\narguments may be provided, alternating tag keys and values (see examples).\nHint: Empty values may be specified with \"\" (bash, cmd.exe) or '\"\"' (PowerShell).",
+          "exclusive": [
+            "detached"
+          ],
+          "name": "release-tag",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "draft": {
+          "description": "Instruct the builder to create the release as a draft. Draft releases are ignored\nby the 'track latest' release policy but can be used through release pinning.\nDraft releases can be marked as final through the API. Releases are created\nas final by default unless this option is given.",
+          "name": "draft",
           "allowNo": false,
           "type": "boolean"
+        },
+        "note": {
+          "description": "The notes for this release",
+          "name": "note",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "os:versions",
+      "id": "push",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
+      "primary": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "os",
-        "versions.js"
+        "push",
+        "index.js"
       ]
     },
-    "preload": {
+    "release:finalize": {
       "aliases": [],
       "args": {
-        "image": {
-          "description": "the image file path",
-          "name": "image",
+        "commitOrId": {
+          "description": "the commit or ID of the release to finalize",
+          "name": "commitOrId",
           "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.",
+      "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 preload balena.img --fleet MyFleet --commit e1f2592fc6ee949e68756d4f4a48e49bff8d72a0",
-        "$ balena preload balena.img --fleet myorg/myfleet --splash-image image.png",
-        "$ balena preload balena.img"
+        "$ balena release finalize a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release finalize 1234567"
       ],
-      "flags": {
-        "fleet": {
-          "char": "f",
-          "description": "fleet name or slug (preferred)",
-          "name": "fleet",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "commit": {
-          "char": "c",
-          "description": "The commit hash of the release to preload. Use \"current\" to specify the current\nrelease (ignored if no appId is given). The current release is usually also the\nlatest, but can be pinned to a specific release. See:\nhttps://www.balena.io/docs/learn/deploy/release-strategy/release-policy/\nhttps://www.balena.io/docs/learn/more/masterclasses/fleet-management/#63-pin-using-the-api\nhttps://github.com/balena-io-examples/staged-releases",
-          "name": "commit",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "splash-image": {
-          "char": "s",
-          "description": "path to a png image to replace the splash screen",
-          "name": "splash-image",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "dont-check-arch": {
-          "description": "disable architecture compatibility check between image and fleet",
-          "name": "dont-check-arch",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "pin-device-to-release": {
-          "char": "p",
-          "description": "pin the preloaded device to the preloaded release on provision",
-          "name": "pin-device-to-release",
-          "allowNo": true,
-          "type": "boolean"
-        },
-        "additional-space": {
-          "description": "expand the image by this amount of bytes instead of automatically estimating the required amount",
-          "name": "additional-space",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "add-certificate": {
-          "description": "Add the given certificate (in PEM format) to /etc/ssl/certs in the preloading container.\nThe file name must end with '.crt' and must not be already contained in the preloader's\n/etc/ssl/certs folder.\nCan be repeated to add multiple certificates.",
-          "name": "add-certificate",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "docker": {
-          "char": "P",
-          "description": "Path to a local docker socket (e.g. /var/run/docker.sock)",
-          "name": "docker",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "dockerHost": {
-          "char": "h",
-          "description": "Docker daemon hostname or IP address (dev machine or balena device) ",
-          "name": "dockerHost",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "dockerPort": {
-          "description": "Docker daemon TCP port number (hint: 2375 for balena devices)",
-          "name": "dockerPort",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "ca": {
-          "description": "Docker host TLS certificate authority file",
-          "name": "ca",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "cert": {
-          "description": "Docker host TLS certificate file",
-          "name": "cert",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "key": {
-          "description": "Docker host TLS key file",
-          "name": "key",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
+      "flags": {},
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "preload",
+      "id": "release:finalize",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
       "authenticated": true,
-      "primary": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "preload",
-        "index.js"
+        "release",
+        "finalize.js"
       ]
     },
-    "push": {
+    "release": {
       "aliases": [],
       "args": {
-        "fleetOrDevice": {
-          "description": "fleet name or slug, or local device IP address or \".local\" hostname",
-          "name": "fleetOrDevice",
+        "commitOrId": {
+          "description": "the commit or ID of the release to get information",
+          "name": "commitOrId",
           "required": true
         }
       },
-      "description": "Build release images on balenaCloud servers or on a local mode device.\n\nBuild release images on balenaCloud servers or on a local mode device.\n\nWhen building on the balenaCloud servers, the given source directory will be\nsent to the remote server. This can be used as a drop-in replacement for the\n\"git push\" deployment method.\n\nWhen building on a local mode device, the given source directory will be\nbuilt on the device, and the resulting containers will be run on the device.\nLogs will be streamed back from the device as part of the same invocation.\nThe web dashboard can be used to switch a device to local mode:\nhttps://www.balena.io/docs/learn/develop/local-mode/\nNote that local mode requires a supervisor version of at least v7.21.0.\nThe logs from only a single service can be shown with the --service flag, and\nshowing only the system logs can be achieved with --system. Note that these\nflags can be used together.\n\nWhen pushing to a local device a live session will be started.\nThe project source folder is watched for filesystem events, and changes\nto files and folders are automatically synchronized to the running\ncontainers. The synchronization is only in one direction, from this machine to\nthe device, and changes made on the device itself may be overwritten.\nThis feature requires a device running supervisor version v9.7.0 or greater.\n\nREGISTRY SECRETS  \nThe --registry-secrets option specifies a JSON or YAML file containing private\nDocker registry usernames and passwords to be used when pulling base images.\nSample registry-secrets YAML file:\n```\n\t'my-registry-server.com:25000':\n\t\tusername: ann\n\t\tpassword: hunter2\n\t'':  # Use the empty string to refer to the Docker Hub\n\t\tusername: mike\n\t\tpassword: cze14\n\t'eu.gcr.io':  # Google Container Registry\n\t\tusername: '_json_key'\n\t\tpassword: '{escaped contents of the GCR keyfile.json file}'\n```\nFor a sample project using registry secrets with the Google Container Registry,\ncheck: https://github.com/balena-io-examples/sample-gcr-registry-secrets\n\nIf the --registry-secrets option is not specified, and a secrets.yml or\nsecrets.json file exists in the balena directory (usually $HOME/.balena),\nthis file will be used instead.\n\nDOCKERIGNORE AND GITIGNORE FILES  \nBy default, the balena CLI will use a single \".dockerignore\" file (if any) at\nthe project root (--source directory) in order to decide which source files to\nexclude from the \"build context\" (tar stream) sent to balenaCloud, Docker\ndaemon or balenaEngine.  In a microservices (multicontainer) fleet, the\nsource directory is the directory that contains the \"docker-compose.yml\" file.\n\nThe --multi-dockerignore (-m) option may be used with microservices\n(multicontainer) fleets that define a docker-compose.yml file. When this\noption is used, each service subdirectory (defined by the `build` or\n`build.context` service properties in the docker-compose.yml file) is\nfiltered separately according to a .dockerignore file defined in the service\nsubdirectory. If no .dockerignore file exists in a service subdirectory, then\nonly the default .dockerignore patterns (see below) apply for that service\nsubdirectory.\n\nWhen the --multi-dockerignore (-m) option is used, the .dockerignore file (if\nany) defined at the overall project root will be used to filter files and\nsubdirectories other than service subdirectories. It will not have any effect\non service subdirectories, whether or not a service subdirectory defines its\nown .dockerignore file. Multiple .dockerignore files are not merged or added\ntogether, and cannot override or extend other files. This behavior maximizes\ncompatibility with the standard docker-compose tool, while still allowing a\nroot .dockerignore file (at the overall project root) to filter files and\nfolders that are outside service subdirectories.\n\nbalena CLI v11 also took .gitignore files into account. This behavior was\ndeprecated in CLI v12 and removed in CLI v13. Please use .dockerignore files\ninstead.\n\nDefault .dockerignore patterns  \nA few default/hardcoded dockerignore patterns are \"merged\" (in memory) with the\npatterns found in the applicable .dockerignore files, in the following order:\n```\n    **/.git\n    < user's patterns from the applicable '.dockerignore' file, if any >\n    !**/.balena\n    !**/.resin\n    !**/Dockerfile\n    !**/Dockerfile.*\n    !**/docker-compose.yml\n```\nThese patterns always apply, whether or not .dockerignore files exist in the\nproject. If necessary, the effect of the `**/.git` pattern may be modified by\nadding exception patterns to the applicable .dockerignore file(s), for example\n`!mysubmodule/.git`. For documentation on pattern format, see:\n- https://docs.docker.com/engine/reference/builder/#dockerignore-file\n- https://www.npmjs.com/package/@balena/dockerignore\n\nNote: the --service and --env flags must come after the fleetOrDevice\nparameter, as per examples.",
+      "description": "Get info for a release.",
       "examples": [
-        "$ balena push myFleet",
-        "$ balena push myFleet --source <source directory>",
-        "$ balena push myFleet -s <source directory>",
-        "$ balena push myFleet --source <source directory> --note \"this is the note for this release\"",
-        "$ balena push myFleet --release-tag key1 \"\" key2 \"value2 with spaces\"",
-        "$ balena push myorg/myfleet",
-        "",
-        "$ balena push 10.0.0.1",
-        "$ balena push 10.0.0.1 --source <source directory>",
-        "$ balena push 10.0.0.1 --service my-service",
-        "$ balena push 10.0.0.1 --env MY_ENV_VAR=value --env my-service:SERVICE_VAR=value",
-        "$ balena push 10.0.0.1 --nolive",
-        "",
-        "$ balena push 23c73a1.local --system",
-        "$ balena push 23c73a1.local --system --service my-service"
+        "$ balena release a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release 1234567"
       ],
       "flags": {
-        "source": {
-          "char": "s",
-          "description": "Source directory to be sent to balenaCloud or balenaOS device\n(default: current working dir)",
-          "name": "source",
-          "default": ".",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "emulated": {
-          "char": "e",
-          "description": "Don't use the faster, native balenaCloud ARM builders; force slower QEMU ARM\nemulation on Intel x86-64 builders. This flag is sometimes used to investigate\nsuspected issues with the balenaCloud backend.",
-          "name": "emulated",
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
           "allowNo": false,
           "type": "boolean"
         },
-        "dockerfile": {
-          "description": "Alternative Dockerfile name/path, relative to the source folder",
-          "name": "dockerfile",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "nocache": {
+        "composition": {
           "char": "c",
-          "description": "Don't use cached layers of previously built images for this project. This\nensures that the latest base image and packages are pulled. Note that build\nlogs may still display the message _\"Pulling previous images for caching\npurposes\" (as the cloud builder needs previous images to compute delta\nupdates), but the logs will not display the \"Using cache\" lines for each\nbuild step of a Dockerfile.",
-          "name": "nocache",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "pull": {
-          "description": "When pushing to a local device, force the base images to be pulled again.\nCurrently this option is ignored when pushing to the balenaCloud builders.",
-          "name": "pull",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "noparent-check": {
-          "description": "Disable project validation check of 'docker-compose.yml' file in parent folder",
-          "name": "noparent-check",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "registry-secrets": {
-          "char": "R",
-          "description": "Path to a local YAML or JSON file containing Docker registry passwords used\nto pull base images. Note that if registry-secrets are not provided on the\ncommand line, a secrets configuration file from the balena directory will be\nused (usually $HOME/.balena/secrets.yml|.json)",
-          "name": "registry-secrets",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "nolive": {
-          "description": "Don't run a live session on this push. The filesystem will not be monitored,\nand changes will not be synchronized to any running containers. Note that both\nthis flag and --detached are required to cause the process to end once the\ninitial build has completed.",
-          "name": "nolive",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "detached": {
-          "char": "d",
-          "description": "When pushing to the cloud, this option will cause the build to start, then\nreturn execution back to the shell, with the status and release ID (if\napplicable).  When pushing to a local mode device, this option will cause\nthe command to not tail logs when the build has completed.",
-          "name": "detached",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "service": {
-          "description": "Reject logs not originating from this service.\nThis can be used in combination with --system and other --service flags.\nOnly valid when pushing to a local mode device.",
-          "name": "service",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "system": {
-          "description": "Only show system logs. This can be used in combination with --service.\nOnly valid when pushing to a local mode device.",
-          "name": "system",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "env": {
-          "description": "When performing a push to device, run the built containers with environment\nvariables provided with this argument. Environment variables can be applied\nto individual services by adding their service name before the argument,\nseparated by a colon, e.g:\n\t--env main:MY_ENV=value\nNote that if the service name cannot be found in the composition, the entire\nleft hand side of the = character will be treated as the variable name.",
-          "name": "env",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "noconvert-eol": {
-          "description": "Don't convert line endings from CRLF (Windows format) to LF (Unix format).",
-          "name": "noconvert-eol",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "multi-dockerignore": {
-          "char": "m",
-          "description": "Have each service use its own .dockerignore file. See \"balena help push\".",
-          "name": "multi-dockerignore",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "release-tag": {
-          "description": "Set release tags if the image build is successful (balenaCloud only). Multiple\narguments may be provided, alternating tag keys and values (see examples).\nHint: Empty values may be specified with \"\" (bash, cmd.exe) or '\"\"' (PowerShell).",
-          "exclusive": [
-            "detached"
-          ],
-          "name": "release-tag",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "draft": {
-          "description": "Instruct the builder to create the release as a draft. Draft releases are ignored\nby the 'track latest' release policy but can be used through release pinning.\nDraft releases can be marked as final through the API. Releases are created\nas final by default unless this option is given.",
-          "name": "draft",
+          "description": "Return the release composition",
+          "name": "composition",
           "allowNo": false,
           "type": "boolean"
-        },
-        "note": {
-          "description": "The notes for this release",
-          "name": "note",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "push",
+      "id": "release",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
-      "enableJsonFlag": false,
-      "primary": true,
+      "enableJsonFlag": true,
+      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "push",
+        "release",
         "index.js"
       ]
     },
+    "release:invalidate": {
+      "aliases": [],
+      "args": {
+        "commitOrId": {
+          "description": "the commit or ID of the release to invalidate",
+          "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.",
+      "examples": [
+        "$ 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": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "release:list",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": true,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "release",
+        "list.js"
+      ]
+    },
+    "release:validate": {
+      "aliases": [],
+      "args": {
+        "commitOrId": {
+          "description": "the commit or ID of the release to validate",
+          "name": "commitOrId",
+          "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.",
+      "examples": [
+        "$ balena release validate a777f7345fe3d655c1c981aa642e5555",
+        "$ balena release validate 1234567"
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "release:validate",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "release",
+        "validate.js"
+      ]
+    },
     "release-asset:delete": {
       "aliases": [],
       "args": {
@@ -4697,7 +4529,190 @@
       "flags": {},
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "whoami",
+      "id": "whoami",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "whoami",
+        "index.js"
+      ]
+    },
+    "os:configure": {
+      "aliases": [],
+      "args": {
+        "image": {
+          "description": "path to a balenaOS image file, e.g. \"rpi3.img\"",
+          "name": "image",
+          "required": true
+        }
+      },
+      "description": "Configure a previously downloaded balenaOS image.\n\nConfigure a previously downloaded balenaOS image for a specific device type\nor fleet.\n\nConfiguration settings such as WiFi authentication will be taken from the\nfollowing sources, in precedence order:\n1. Command-line options like `--config-wifi-ssid`\n2. A given `config.json` file specified with the `--config` option.\n3. User input through interactive prompts (text menus).\n\nThe --device-type option is used to override the fleet's default device type,\nin case of a fleet with mixed device types.\n\nThe '--dev' option is used to configure balenaOS to operate in development mode,\nallowing unauthenticated root ssh access and exposing network ports such as\nbalenaEngine's 2375 (unencrypted). This option causes `\"developmentMode\": true`\nto be inserted in the 'config.json' file in the image's boot partition. Development\nmode (as a configurable option) is applicable to balenaOS releases from early\n2022. Older releases have separate development and production balenaOS images\nthat cannot be reconfigured through 'config.json' or the '--dev' option. Do not\nconfuse the balenaOS \"development mode\" with a device's \"local mode\", the latter\nbeing a supervisor feature that allows the \"balena push\" command to push a user's\napplication directly to a device in the local network.\n\nThe '--secureBoot' option is used to configure a balenaOS installer image to opt-in\nsecure boot and disk encryption.\n\nThe --system-connection (-c) option is used to inject NetworkManager connection\nprofiles for additional network interfaces, such as cellular/GSM or additional\nWiFi or ethernet connections. This option may be passed multiple times in case there\nare multiple files to inject. See connection profile examples and reference at:\nhttps://www.balena.io/docs/reference/OS/network/2.x/\nhttps://developer.gnome.org/NetworkManager/stable/ref-settings.html\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 os configure ../path/rpi3.img --device 7cf02a6",
+        "$ balena os configure ../path/rpi3.img --fleet myorg/myfleet",
+        "$ balena os configure ../path/rpi3.img -f myorg/myfleet --device-type raspberrypi3",
+        "$ balena os configure ../path/rpi3.img --config myWifiConfig.json"
+      ],
+      "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",
+          "exclusive": [
+            "fleet",
+            "device-type",
+            "config",
+            "provisioning-key-name",
+            "provisioning-key-expiry-date"
+          ],
+          "name": "device",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "config": {
+          "description": "path to a pre-generated config.json file to be injected in the OS image",
+          "exclusive": [
+            "fleet",
+            "device",
+            "advanced",
+            "config-app-update-poll-interval",
+            "config-network",
+            "config-wifi-key",
+            "config-wifi-ssid",
+            "dev",
+            "secureBoot",
+            "device-type",
+            "initial-device-name",
+            "provisioning-key-name",
+            "provisioning-key-expiry-date"
+          ],
+          "name": "config",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "advanced": {
+          "char": "v",
+          "description": "ask advanced configuration questions (when in interactive mode)",
+          "name": "advanced",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "config-app-update-poll-interval": {
+          "description": "supervisor cloud polling interval in minutes (e.g. for variable updates)",
+          "name": "config-app-update-poll-interval",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "config-network": {
+          "description": "device network type (non-interactive configuration)",
+          "name": "config-network",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "ethernet",
+            "wifi"
+          ],
+          "type": "option"
+        },
+        "config-wifi-key": {
+          "description": "WiFi key (password) (non-interactive configuration)",
+          "name": "config-wifi-key",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "config-wifi-ssid": {
+          "description": "WiFi SSID (network name) (non-interactive configuration)",
+          "name": "config-wifi-ssid",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "dev": {
+          "description": "Configure balenaOS to operate in development mode",
+          "name": "dev",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "secureBoot": {
+          "description": "Configure balenaOS installer to opt-in secure boot and disk encryption",
+          "name": "secureBoot",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "device-type": {
+          "dependsOn": [
+            "fleet"
+          ],
+          "description": "device type slug (e.g. \"raspberrypi3\") to override the fleet device type",
+          "name": "device-type",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "initial-device-name": {
+          "description": "This option will set the device name when the device provisions",
+          "name": "initial-device-name",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "provisioning-key-name": {
+          "description": "custom key name assigned to generated provisioning api key",
+          "exclusive": [
+            "config",
+            "device"
+          ],
+          "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)",
+          "exclusive": [
+            "config",
+            "device"
+          ],
+          "name": "provisioning-key-expiry-date",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "system-connection": {
+          "char": "c",
+          "description": "paths to local files to place into the 'system-connections' directory",
+          "name": "system-connection",
+          "required": false,
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "os:configure",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -4708,107 +4723,120 @@
       "relativePath": [
         "build",
         "commands",
-        "whoami",
-        "index.js"
+        "os",
+        "configure.js"
       ]
     },
-    "release:finalize": {
+    "os:download": {
       "aliases": [],
       "args": {
-        "commitOrId": {
-          "description": "the commit or ID of the release to finalize",
-          "name": "commitOrId",
+        "type": {
+          "description": "the device type",
+          "name": "type",
           "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.",
+      "description": "Download an unconfigured OS image.\n\nDownload an unconfigured OS image for the specified device type.\nCheck available device types with 'balena device-type list'.\n\nNote: Currently this command only works with balenaCloud, not openBalena.\nIf using openBalena, please download the OS from: https://www.balena.io/os/\n\nThe '--version' option is used to select the balenaOS version. If omitted,\nthe latest released version is downloaded (and if only pre-release versions\nexist, the latest pre-release version is downloaded).\n\nUse '--type' to specify the type of OS download\nIf omitted, the default type for the specified device type-version combination is used.\nSome OS download types may not be available for certain device types and versions.\n\nUse '--version menu' or '--version menu-esr' to interactively select the\nOS version. The latter lists ESR versions which are only available for\ndownload on Production and Enterprise plans. See also:\nhttps://www.balena.io/docs/reference/OS/extended-support-release/\n\nDevelopment images can be selected by appending `.dev` to the version.",
       "examples": [
-        "$ balena release finalize a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release finalize 1234567"
+        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img",
+        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2.101.7",
+        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2022.7.0",
+        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version ^2.90.0",
+        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2.60.1+rev1",
+        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2.60.1+rev1.dev",
+        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version 2021.10.2.prod",
+        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version latest",
+        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version menu",
+        "$ balena os download raspberrypi3 -o ../foo/bar/raspberrypi3.img --version menu-esr",
+        "$ balena os download generic-amd64 -o ../foo/bar/generic-amd64.img --type installation-media"
       ],
-      "flags": {},
+      "flags": {
+        "output": {
+          "char": "o",
+          "description": "output path",
+          "name": "output",
+          "required": true,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "version": {
+          "description": "version number (ESR or non-ESR versions),\nor semver range (non-ESR versions only),\nor 'latest' (excludes invalidated & pre-releases),\nor 'menu' (interactive menu, non-ESR versions),\nor 'menu-esr' (interactive menu, ESR versions)",
+          "name": "version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "type": {
+          "description": "'disk-image' (for flashing onto device system disk/storage)\nor 'installation-media' (for creating installation media to automatically erase, format, and install balenaOS on a device)",
+          "name": "type",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "installation-media",
+            "disk-image"
+          ],
+          "type": "option"
+        }
+      },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "release:finalize",
+      "id": "os:download",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "release",
-        "finalize.js"
+        "os",
+        "download.js"
       ]
     },
-    "release": {
+    "os:initialize": {
       "aliases": [],
       "args": {
-        "commitOrId": {
-          "description": "the commit or ID of the release to get information",
-          "name": "commitOrId",
+        "image": {
+          "description": "path to OS image",
+          "name": "image",
           "required": true
         }
       },
-      "description": "Get info for a release.",
+      "description": "Initialize an os image for a device.\n\n\t\tInitialize an os image for a device with a previously\n\t\tconfigured operating system image and flash the\n\t\tan external storage drive or the device's storage\n\t\tmedium depending on the device type.\n\t\t\n\nNote: Initializing the device may ask for administrative permissions\nbecause we need to access the raw devices directly.",
       "examples": [
-        "$ balena release a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release 1234567"
+        "$ balena os initialize ../path/rpi.img --type raspberry-pi"
       ],
       "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
+        "type": {
+          "char": "t",
+          "description": "device type (Check available types with `balena device-type list`)",
+          "name": "type",
+          "required": true,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         },
-        "composition": {
-          "char": "c",
-          "description": "Return the release composition",
-          "name": "composition",
+        "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": "release",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": true,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "release",
-        "index.js"
-      ]
-    },
-    "release:invalidate": {
-      "aliases": [],
-      "args": {
-        "commitOrId": {
-          "description": "the commit or ID of the release to invalidate",
-          "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.",
-      "examples": [
-        "$ balena release invalidate a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release invalidate 1234567"
-      ],
-      "flags": {},
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "release:invalidate",
+      "id": "os:initialize",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
@@ -4819,81 +4847,53 @@
       "relativePath": [
         "build",
         "commands",
-        "release",
-        "invalidate.js"
+        "os",
+        "initialize.js"
       ]
     },
-    "release:list": {
+    "os:versions": {
       "aliases": [],
       "args": {
-        "fleet": {
-          "description": "fleet name or slug (preferred)",
-          "name": "fleet",
+        "type": {
+          "description": "device type",
+          "name": "type",
           "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": "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 release list myorg/myfleet"
+        "$ balena os versions raspberrypi3"
       ],
       "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
+        "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": "release:list",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": true,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "release",
-        "list.js"
-      ]
-    },
-    "release:validate": {
-      "aliases": [],
-      "args": {
-        "commitOrId": {
-          "description": "the commit or ID of the release to validate",
-          "name": "commitOrId",
-          "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.",
-      "examples": [
-        "$ balena release validate a777f7345fe3d655c1c981aa642e5555",
-        "$ balena release validate 1234567"
-      ],
-      "flags": {},
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "release:validate",
+      "id": "os:versions",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "release",
-        "validate.js"
+        "os",
+        "versions.js"
       ]
     }
   },
-  "version": "25.1.2"
+  "version": "25.1.3"
 }