balena-cli 25.2.7 → 25.2.8

package/CHANGELOG.md

@@ -4,6 +4,10 @@ All notable changes to this project will be documented in this file
 automatically by Versionist. DO NOT EDIT THIS FILE MANUALLY!
 This project adheres to [Semantic Versioning](http://semver.org/).
 
+## 25.2.8 - 2026-10-21
+
+* Update actions/setup-node action to v7 [balena-renovate[bot]]
+
 ## 25.2.7 - 2026-10-21
 
 * Republish with nodejs ^24.22.1 [Thodoris Greasidis]

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "balena-cli",
-  "version": "25.2.7",
+  "version": "25.2.8",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "balena-cli",
-      "version": "25.2.7",
+      "version": "25.2.8",
       "hasInstallScript": true,
       "license": "Apache-2.0",
       "dependencies": {

package/oclif.manifest.json

@@ -110,106 +110,6 @@
         "revoke.js"
       ]
     },
-    "app:create": {
-      "aliases": [],
-      "args": {
-        "name": {
-          "description": "app name",
-          "name": "name",
-          "required": true
-        }
-      },
-      "description": "Create an app.\n\nCreate a new balena app.\n\nYou can specify the organization the app 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 app'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 app create MyApp",
-        "$ balena app create MyApp --organization mmyorg",
-        "$ balena app create MyApp -o myorg --type raspberry-pi"
-      ],
-      "flags": {
-        "organization": {
-          "char": "o",
-          "description": "handle of the organization the app should belong to",
-          "name": "organization",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "type": {
-          "char": "t",
-          "description": "app device type (Check available types with `balena device-type list`)",
-          "name": "type",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "app:create",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "app",
-        "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 +312,106 @@
         "index.js"
       ]
     },
+    "app:create": {
+      "aliases": [],
+      "args": {
+        "name": {
+          "description": "app name",
+          "name": "name",
+          "required": true
+        }
+      },
+      "description": "Create an app.\n\nCreate a new balena app.\n\nYou can specify the organization the app 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 app'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 app create MyApp",
+        "$ balena app create MyApp --organization mmyorg",
+        "$ balena app create MyApp -o myorg --type raspberry-pi"
+      ],
+      "flags": {
+        "organization": {
+          "char": "o",
+          "description": "handle of the organization the app should belong to",
+          "name": "organization",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "type": {
+          "char": "t",
+          "description": "app device type (Check available types with `balena device-type list`)",
+          "name": "type",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "app:create",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "app",
+        "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"
+      ]
+    },
     "config:generate": {
       "aliases": [],
       "args": {},
@@ -3084,6 +3084,30 @@
         "flash.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"
+      ]
+    },
     "login": {
       "aliases": [],
       "args": {
@@ -3209,30 +3233,6 @@
         "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:create": {
       "aliases": [],
       "args": {
@@ -3365,146 +3365,16 @@
         "rm.js"
       ]
     },
-    "preload": {
+    "os:configure": {
       "aliases": [],
       "args": {
         "image": {
-          "description": "the image file path",
+          "description": "path to a balenaOS image file, e.g. \"rpi3.img\"",
           "name": "image",
           "required": true
         }
       },
-      "description": "Preload a release on a disk image (or Edison zip archive).\n\nPreload a release (service images/containers) from a balena fleet, and optionally\na balenaOS splash screen, in a previously downloaded '.img' balenaOS image file\nin the local disk (a zip file is only accepted for the Intel Edison device type).\nAfter preloading, the balenaOS image file can be flashed to a device's SD card.\nWhen the device boots, it will not need to download the release, as it was\npreloaded. This is usually combined with release pinning\n(https://www.balena.io/docs/learn/deploy/release-strategy/release-policy/)\nto avoid the device downloading a newer release straight away, if available.\nCheck also the Preloading and Preregistering section of the balena CLI's advanced\nmasterclass document:\nhttps://www.balena.io/docs/learn/more/masterclasses/advanced-cli/#5-preloading-and-preregistering\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).\n\nNote that the this command requires Docker to be installed, as further detailed\nin the balena CLI's installation instructions:\nhttps://github.com/balena-io/balena-cli/blob/master/INSTALL.md\nThe `--dockerHost` and `--dockerPort` flags allow a remote Docker engine to\nbe used, however the image file must be accessible to the remote Docker engine\non the same path given on the command line. This is because Docker's bind mount\nfeature is used to \"share\" the image with a container that performs the preload.",
-      "examples": [
-        "$ balena preload balena.img --fleet MyFleet --commit e1f2592fc6ee949e68756d4f4a48e49bff8d72a0",
-        "$ balena preload balena.img --fleet myorg/myfleet --splash-image image.png",
-        "$ balena preload balena.img"
-      ],
-      "flags": {
-        "fleet": {
-          "char": "f",
-          "description": "fleet name or slug (preferred)",
-          "name": "fleet",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "commit": {
-          "char": "c",
-          "description": "The commit hash of the release to preload. Use \"current\" to specify the current\nrelease (ignored if no appId is given). The current release is usually also the\nlatest, but can be pinned to a specific release. See:\nhttps://www.balena.io/docs/learn/deploy/release-strategy/release-policy/\nhttps://www.balena.io/docs/learn/more/masterclasses/fleet-management/#63-pin-using-the-api\nhttps://github.com/balena-io-examples/staged-releases",
-          "name": "commit",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "splash-image": {
-          "char": "s",
-          "description": "path to a png image to replace the splash screen",
-          "name": "splash-image",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "dont-check-arch": {
-          "description": "disable architecture compatibility check between image and fleet",
-          "name": "dont-check-arch",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "pin-device-to-release": {
-          "char": "p",
-          "description": "pin the preloaded device to the preloaded release on provision",
-          "name": "pin-device-to-release",
-          "allowNo": true,
-          "type": "boolean"
-        },
-        "additional-space": {
-          "description": "expand the image by this amount of bytes instead of automatically estimating the required amount",
-          "name": "additional-space",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "add-certificate": {
-          "description": "Add the given certificate (in PEM format) to /etc/ssl/certs in the preloading container.\nThe file name must end with '.crt' and must not be already contained in the preloader's\n/etc/ssl/certs folder.\nCan be repeated to add multiple certificates.",
-          "name": "add-certificate",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "docker": {
-          "char": "P",
-          "description": "Path to a local docker socket (e.g. /var/run/docker.sock)",
-          "name": "docker",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "dockerHost": {
-          "char": "h",
-          "description": "Docker daemon hostname or IP address (dev machine or balena device) ",
-          "name": "dockerHost",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "dockerPort": {
-          "description": "Docker daemon TCP port number (hint: 2375 for balena devices)",
-          "name": "dockerPort",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "ca": {
-          "description": "Docker host TLS certificate authority file",
-          "name": "ca",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "cert": {
-          "description": "Docker host TLS certificate file",
-          "name": "cert",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "key": {
-          "description": "Docker host TLS key file",
-          "name": "key",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "preload",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "primary": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "preload",
-        "index.js"
-      ]
-    },
-    "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. This command overwrites the image's `config.json` with a new\none generated from the options provided to the command, or with the file\npassed via the `--config` option.\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": "Configure a previously downloaded balenaOS image.\n\nConfigure a previously downloaded balenaOS image for a specific device type\nor fleet. This command overwrites the image's `config.json` with a new\none generated from the options provided to the command, or with the file\npassed via the `--config` option.\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",
@@ -3845,6 +3715,136 @@
         "versions.js"
       ]
     },
+    "preload": {
+      "aliases": [],
+      "args": {
+        "image": {
+          "description": "the image file path",
+          "name": "image",
+          "required": true
+        }
+      },
+      "description": "Preload a release on a disk image (or Edison zip archive).\n\nPreload a release (service images/containers) from a balena fleet, and optionally\na balenaOS splash screen, in a previously downloaded '.img' balenaOS image file\nin the local disk (a zip file is only accepted for the Intel Edison device type).\nAfter preloading, the balenaOS image file can be flashed to a device's SD card.\nWhen the device boots, it will not need to download the release, as it was\npreloaded. This is usually combined with release pinning\n(https://www.balena.io/docs/learn/deploy/release-strategy/release-policy/)\nto avoid the device downloading a newer release straight away, if available.\nCheck also the Preloading and Preregistering section of the balena CLI's advanced\nmasterclass document:\nhttps://www.balena.io/docs/learn/more/masterclasses/advanced-cli/#5-preloading-and-preregistering\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).\n\nNote that the this command requires Docker to be installed, as further detailed\nin the balena CLI's installation instructions:\nhttps://github.com/balena-io/balena-cli/blob/master/INSTALL.md\nThe `--dockerHost` and `--dockerPort` flags allow a remote Docker engine to\nbe used, however the image file must be accessible to the remote Docker engine\non the same path given on the command line. This is because Docker's bind mount\nfeature is used to \"share\" the image with a container that performs the preload.",
+      "examples": [
+        "$ balena preload balena.img --fleet MyFleet --commit e1f2592fc6ee949e68756d4f4a48e49bff8d72a0",
+        "$ balena preload balena.img --fleet myorg/myfleet --splash-image image.png",
+        "$ balena preload balena.img"
+      ],
+      "flags": {
+        "fleet": {
+          "char": "f",
+          "description": "fleet name or slug (preferred)",
+          "name": "fleet",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "commit": {
+          "char": "c",
+          "description": "The commit hash of the release to preload. Use \"current\" to specify the current\nrelease (ignored if no appId is given). The current release is usually also the\nlatest, but can be pinned to a specific release. See:\nhttps://www.balena.io/docs/learn/deploy/release-strategy/release-policy/\nhttps://www.balena.io/docs/learn/more/masterclasses/fleet-management/#63-pin-using-the-api\nhttps://github.com/balena-io-examples/staged-releases",
+          "name": "commit",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "splash-image": {
+          "char": "s",
+          "description": "path to a png image to replace the splash screen",
+          "name": "splash-image",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "dont-check-arch": {
+          "description": "disable architecture compatibility check between image and fleet",
+          "name": "dont-check-arch",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "pin-device-to-release": {
+          "char": "p",
+          "description": "pin the preloaded device to the preloaded release on provision",
+          "name": "pin-device-to-release",
+          "allowNo": true,
+          "type": "boolean"
+        },
+        "additional-space": {
+          "description": "expand the image by this amount of bytes instead of automatically estimating the required amount",
+          "name": "additional-space",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "add-certificate": {
+          "description": "Add the given certificate (in PEM format) to /etc/ssl/certs in the preloading container.\nThe file name must end with '.crt' and must not be already contained in the preloader's\n/etc/ssl/certs folder.\nCan be repeated to add multiple certificates.",
+          "name": "add-certificate",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "docker": {
+          "char": "P",
+          "description": "Path to a local docker socket (e.g. /var/run/docker.sock)",
+          "name": "docker",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "dockerHost": {
+          "char": "h",
+          "description": "Docker daemon hostname or IP address (dev machine or balena device) ",
+          "name": "dockerHost",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "dockerPort": {
+          "description": "Docker daemon TCP port number (hint: 2375 for balena devices)",
+          "name": "dockerPort",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "ca": {
+          "description": "Docker host TLS certificate authority file",
+          "name": "ca",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "cert": {
+          "description": "Docker host TLS certificate file",
+          "name": "cert",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "key": {
+          "description": "Docker host TLS key file",
+          "name": "key",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "preload",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "primary": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "preload",
+        "index.js"
+      ]
+    },
     "push": {
       "aliases": [],
       "args": {
@@ -4192,6 +4192,30 @@
         "validate.js"
       ]
     },
+    "settings": {
+      "aliases": [],
+      "args": {},
+      "description": "Print current settings.\n\nUse this command to display the current balena CLI settings.",
+      "examples": [
+        "$ balena settings"
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "settings",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "settings",
+        "index.js"
+      ]
+    },
     "release-asset:delete": {
       "aliases": [],
       "args": {
@@ -4407,30 +4431,6 @@
         "upload.js"
       ]
     },
-    "settings": {
-      "aliases": [],
-      "args": {},
-      "description": "Print current settings.\n\nUse this command to display the current balena CLI settings.",
-      "examples": [
-        "$ balena settings"
-      ],
-      "flags": {},
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "settings",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "settings",
-        "index.js"
-      ]
-    },
     "ssh-key:add": {
       "aliases": [],
       "args": {
@@ -4895,5 +4895,5 @@
       ]
     }
   },
-  "version": "25.2.7"
+  "version": "25.2.8"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "balena-cli",
-  "version": "25.2.7",
+  "version": "25.2.8",
   "description": "The official balena Command Line Interface",
   "main": "./build/app.js",
   "homepage": "https://github.com/balena-io/balena-cli",
@@ -258,6 +258,6 @@
     }
   },
   "versionist": {
-    "publishedAt": "2026-10-21T14:44:15.996Z"
+    "publishedAt": "2026-10-21T17:56:00.460Z"
   }
 }