balena-cli 22.5.6-build-renovate-aws-actions-configure-aws-credentials-5-x-2944b39b3867a1dd0a575c51dd232c6fea70e9fb-1 → 22.5.6-build-renovate-apple-actions-import-codesign-certs-3-x-a0d90954ca5b70af4b7cd88fbe1e09db72dee7fb-1

package/CHANGELOG.md

@@ -6,7 +6,7 @@ This project adheres to [Semantic Versioning](http://semver.org/).
 
 ## 22.5.6 - 2025-11-14
 
-* Update aws-actions/configure-aws-credentials action to v5 [balena-renovate[bot]]
+* Update apple-actions/import-codesign-certs action to v3 [balena-renovate[bot]]
 
 ## 22.5.5 - 2025-11-14
 

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "balena-cli",
-  "version": "22.5.6-build-renovate-aws-actions-configure-aws-credentials-5-x-2944b39b3867a1dd0a575c51dd232c6fea70e9fb-1",
+  "version": "22.5.6-build-renovate-apple-actions-import-codesign-certs-3-x-a0d90954ca5b70af4b7cd88fbe1e09db72dee7fb-1",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "balena-cli",
-      "version": "22.5.6-build-renovate-aws-actions-configure-aws-credentials-5-x-2944b39b3867a1dd0a575c51dd232c6fea70e9fb-1",
+      "version": "22.5.6-build-renovate-apple-actions-import-codesign-certs-3-x-a0d90954ca5b70af4b7cd88fbe1e09db72dee7fb-1",
       "hasInstallScript": true,
       "license": "Apache-2.0",
       "dependencies": {

package/oclif.manifest.json

@@ -365,6 +365,56 @@
         "index.js"
       ]
     },
+    "block:create": {
+      "aliases": [],
+      "args": {
+        "name": {
+          "description": "block name",
+          "name": "name",
+          "required": true
+        }
+      },
+      "description": "Create an block.\n\nCreate a new balena block.\n\nYou can specify the organization the block should belong to using\nthe `--organization` option. The organization's handle, not its name,\nshould be provided. Organization handles can be listed with the\n`balena organization list` command.\n\nThe block's default device type is specified with the `--type` option.\nThe `balena device-type list` command can be used to list the available\ndevice types.\n\nInteractive dropdowns will be shown for selection if no device type or\norganization is specified and there are multiple options to choose from.\nIf there is a single option to choose from, it will be chosen automatically.\nThis interactive behavior can be disabled by explicitly specifying a device\ntype and organization.",
+      "examples": [
+        "$ balena block create MyBlock",
+        "$ balena block create MyBlock --organization mmyorg",
+        "$ balena block create MyBlock -o myorg --type raspberry-pi"
+      ],
+      "flags": {
+        "organization": {
+          "char": "o",
+          "description": "handle of the organization the block should belong to",
+          "name": "organization",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "type": {
+          "char": "t",
+          "description": "block device type (Check available types with `balena device-type list`)",
+          "name": "type",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "block:create",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "block",
+        "create.js"
+      ]
+    },
     "config:generate": {
       "aliases": [],
       "args": {},
@@ -715,56 +765,6 @@
         "write.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"
-      ]
-    },
     "deploy": {
       "aliases": [],
       "args": {
@@ -3438,134 +3438,299 @@
         "index.js"
       ]
     },
-    "os:build-config": {
+    "push": {
       "aliases": [],
       "args": {
-        "image": {
-          "description": "os image",
-          "name": "image",
-          "required": true
-        },
-        "device-type": {
-          "description": "device type",
-          "name": "device-type",
+        "fleetOrDevice": {
+          "description": "fleet name or slug, or local device IP address or \".local\" hostname",
+          "name": "fleetOrDevice",
           "required": true
         }
       },
-      "description": "Prepare a configuration file for use by the 'os configure' command.\n\nInteractively generate a configuration file that can then be used as\nnon-interactive input by the 'balena os configure' command.\n\nDEPRECATED: Use 'balena config generate' instead.",
+      "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 build-config ../path/rpi3.img raspberrypi3 --output rpi3-config.json",
-        "$ balena os configure ../path/rpi3.img --device 7cf02a6 --config rpi3-config.json"
+        "$ 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": {
-        "advanced": {
-          "char": "v",
-          "description": "show advanced configuration options",
-          "name": "advanced",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "output": {
-          "char": "o",
-          "description": "path to output JSON file",
-          "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"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "os:build-config",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "os",
-        "build-config.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 -f myorg/myfleet --device-type raspberrypi3 --config myWifiConfig.json"
-      ],
-      "flags": {
-        "advanced": {
-          "char": "v",
-          "description": "ask advanced configuration questions (when in interactive mode)",
-          "name": "advanced",
+        },
+        "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"
         },
-        "fleet": {
-          "char": "f",
-          "description": "fleet name or slug (preferred)",
-          "exclusive": [
-            "device"
-          ],
-          "name": "fleet",
+        "dockerfile": {
+          "description": "Alternative Dockerfile name/path, relative to the source folder",
+          "name": "dockerfile",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "config": {
-          "description": "path to a pre-generated config.json file to be injected in the OS image",
-          "exclusive": [
-            "provisioning-key-name",
-            "provisioning-key-expiry-date"
-          ],
-          "name": "config",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
+        "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"
         },
-        "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"
+        "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"
         },
-        "config-network": {
-          "description": "device network type (non-interactive configuration)",
-          "name": "config-network",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "options": [
-            "ethernet",
-            "wifi"
-          ],
-          "type": "option"
+        "noparent-check": {
+          "description": "Disable project validation check of 'docker-compose.yml' file in parent folder",
+          "name": "noparent-check",
+          "allowNo": false,
+          "type": "boolean"
         },
-        "config-wifi-key": {
-          "description": "WiFi key (password) (non-interactive configuration)",
-          "name": "config-wifi-key",
+        "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"
         },
-        "config-wifi-ssid": {
-          "description": "WiFi SSID (network name) (non-interactive configuration)",
-          "name": "config-wifi-ssid",
+        "nolive": {
+          "description": "Don't run a live session on this push. The filesystem will not be monitored,\nand changes will not be synchronized to any running containers. Note that both\nthis flag and --detached are required to cause the process to end once the\ninitial build has completed.",
+          "name": "nolive",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "detached": {
+          "char": "d",
+          "description": "When pushing to the cloud, this option will cause the build to start, then\nreturn execution back to the shell, with the status and release ID (if\napplicable).  When pushing to a local mode device, this option will cause\nthe command to not tail logs when the build has completed.",
+          "name": "detached",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "service": {
+          "description": "Reject logs not originating from this service.\nThis can be used in combination with --system and other --service flags.\nOnly valid when pushing to a local mode device.",
+          "name": "service",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "system": {
+          "description": "Only show system logs. This can be used in combination with --service.\nOnly valid when pushing to a local mode device.",
+          "name": "system",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "env": {
+          "description": "When performing a push to device, run the built containers with environment\nvariables provided with this argument. Environment variables can be applied\nto individual services by adding their service name before the argument,\nseparated by a colon, e.g:\n\t--env main:MY_ENV=value\nNote that if the service name cannot be found in the composition, the entire\nleft hand side of the = character will be treated as the variable name.",
+          "name": "env",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "noconvert-eol": {
+          "description": "Don't convert line endings from CRLF (Windows format) to LF (Unix format).",
+          "name": "noconvert-eol",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "multi-dockerignore": {
+          "char": "m",
+          "description": "Have each service use its own .dockerignore file. See \"balena help push\".",
+          "name": "multi-dockerignore",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "release-tag": {
+          "description": "Set release tags if the image build is successful (balenaCloud only). Multiple\narguments may be provided, alternating tag keys and values (see examples).\nHint: Empty values may be specified with \"\" (bash, cmd.exe) or '\"\"' (PowerShell).",
+          "exclusive": [
+            "detached"
+          ],
+          "name": "release-tag",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "draft": {
+          "description": "Instruct the builder to create the release as a draft. Draft releases are ignored\nby the 'track latest' release policy but can be used through release pinning.\nDraft releases can be marked as final through the API. Releases are created\nas final by default unless this option is given.",
+          "name": "draft",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "note": {
+          "description": "The notes for this release",
+          "name": "note",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "push",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "primary": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "push",
+        "index.js"
+      ]
+    },
+    "os:build-config": {
+      "aliases": [],
+      "args": {
+        "image": {
+          "description": "os image",
+          "name": "image",
+          "required": true
+        },
+        "device-type": {
+          "description": "device type",
+          "name": "device-type",
+          "required": true
+        }
+      },
+      "description": "Prepare a configuration file for use by the 'os configure' command.\n\nInteractively generate a configuration file that can then be used as\nnon-interactive input by the 'balena os configure' command.\n\nDEPRECATED: Use 'balena config generate' instead.",
+      "examples": [
+        "$ balena os build-config ../path/rpi3.img raspberrypi3 --output rpi3-config.json",
+        "$ balena os configure ../path/rpi3.img --device 7cf02a6 --config rpi3-config.json"
+      ],
+      "flags": {
+        "advanced": {
+          "char": "v",
+          "description": "show advanced configuration options",
+          "name": "advanced",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "output": {
+          "char": "o",
+          "description": "path to output JSON file",
+          "name": "output",
+          "required": true,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "os:build-config",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "os",
+        "build-config.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 -f myorg/myfleet --device-type raspberrypi3 --config myWifiConfig.json"
+      ],
+      "flags": {
+        "advanced": {
+          "char": "v",
+          "description": "ask advanced configuration questions (when in interactive mode)",
+          "name": "advanced",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "fleet": {
+          "char": "f",
+          "description": "fleet name or slug (preferred)",
+          "exclusive": [
+            "device"
+          ],
+          "name": "fleet",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "config": {
+          "description": "path to a pre-generated config.json file to be injected in the OS image",
+          "exclusive": [
+            "provisioning-key-name",
+            "provisioning-key-expiry-date"
+          ],
+          "name": "config",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "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"
@@ -3744,246 +3909,81 @@
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
-        },
-        "drive": {
-          "char": "d",
-          "description": "the drive to write the image to, eg. `/dev/sdb` or `/dev/mmcblk0`.\nCareful with this as you can erase your hard drive.\nCheck `balena util available-drives` for available options.",
-          "name": "drive",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "yes": {
-          "char": "y",
-          "description": "answer \"yes\" to all questions (non interactive use)",
-          "name": "yes",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "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",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "include-draft": {
-          "description": "include pre-release balenaOS versions",
-          "name": "include-draft",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "os:versions",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "os",
-        "versions.js"
-      ]
-    },
-    "push": {
-      "aliases": [],
-      "args": {
-        "fleetOrDevice": {
-          "description": "fleet name or slug, or local device IP address or \".local\" hostname",
-          "name": "fleetOrDevice",
-          "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.",
-      "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"
-      ],
-      "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",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "dockerfile": {
-          "description": "Alternative Dockerfile name/path, relative to the source folder",
-          "name": "dockerfile",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "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,
-          "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",
+        },
+        "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": true,
+          "multiple": false,
           "type": "option"
         },
-        "draft": {
-          "description": "Instruct the builder to create the release as a draft. Draft releases are ignored\nby the 'track latest' release policy but can be used through release pinning.\nDraft releases can be marked as final through the API. Releases are created\nas final by default unless this option is given.",
-          "name": "draft",
+        "yes": {
+          "char": "y",
+          "description": "answer \"yes\" to all questions (non interactive use)",
+          "name": "yes",
+          "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",
           "allowNo": false,
           "type": "boolean"
         },
-        "note": {
-          "description": "The notes for this release",
-          "name": "note",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
+        "include-draft": {
+          "description": "include pre-release balenaOS versions",
+          "name": "include-draft",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "push",
+      "id": "os:versions",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
-      "primary": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "push",
-        "index.js"
+        "os",
+        "versions.js"
       ]
     },
     "release:finalize": {
@@ -4173,6 +4173,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": {
@@ -4389,27 +4413,64 @@
         "upload.js"
       ]
     },
-    "settings": {
+    "support": {
       "aliases": [],
-      "args": {},
-      "description": "Print current settings.\n\nUse this command to display the current balena CLI settings.",
+      "args": {
+        "action": {
+          "description": "enable|disable support access",
+          "name": "action",
+          "options": [
+            "enable",
+            "disable"
+          ]
+        }
+      },
+      "description": "Grant or revoke support access for devices or fleets.\n\nGrant or revoke balena support agent access to devices or fleets\non balenaCloud. (This command does not apply to openBalena.)\nAccess will be automatically revoked once the specified duration has elapsed.\n\nDuration defaults to 24h, but can be specified using --duration flag in days\nor hours, e.g. '12h', '2d'.\n\nBoth --device and --fleet flags accept multiple values, specified as\na comma-separated list (with no spaces).\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).",
       "examples": [
-        "$ balena settings"
+        "balena support enable --device ab346f,cd457a --duration 3d",
+        "balena support enable --fleet myFleet --duration 12h",
+        "balena support disable -f myorg/myfleet"
       ],
-      "flags": {},
+      "flags": {
+        "device": {
+          "char": "d",
+          "description": "comma-separated list (no spaces) of device UUIDs",
+          "name": "device",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "fleet": {
+          "char": "f",
+          "description": "comma-separated list (no spaces) of fleet names or slugs (preferred)",
+          "name": "fleet",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "duration": {
+          "char": "t",
+          "description": "length of time to enable support for, in (h)ours or (d)ays, e.g. 12h, 2d",
+          "name": "duration",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "settings",
+      "id": "support",
       "pluginAlias": "balena-cli",
       "pluginName": "balena-cli",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": false,
+      "authenticated": true,
       "isESM": false,
       "relativePath": [
         "build",
         "commands",
-        "settings",
+        "support",
         "index.js"
       ]
     },
@@ -4561,67 +4622,6 @@
         "rm.js"
       ]
     },
-    "support": {
-      "aliases": [],
-      "args": {
-        "action": {
-          "description": "enable|disable support access",
-          "name": "action",
-          "options": [
-            "enable",
-            "disable"
-          ]
-        }
-      },
-      "description": "Grant or revoke support access for devices or fleets.\n\nGrant or revoke balena support agent access to devices or fleets\non balenaCloud. (This command does not apply to openBalena.)\nAccess will be automatically revoked once the specified duration has elapsed.\n\nDuration defaults to 24h, but can be specified using --duration flag in days\nor hours, e.g. '12h', '2d'.\n\nBoth --device and --fleet flags accept multiple values, specified as\na comma-separated list (with no spaces).\n\nFleets may be specified by fleet name or slug. Fleet slugs are\nthe recommended option, as they are unique and unambiguous. Slugs can be\nlisted with the `balena fleet list` command. Note that slugs may change if the\nfleet is renamed. Fleet names are not unique and may result in  \"Fleet is\nambiguous\" errors at any time (even if it \"used to work in the past\"), for\nexample if the name clashes with a newly created public fleet, or with fleets\nfrom other balena accounts that you may be invited to join under any role.\nFor this reason, fleet names are especially discouraged in scripts (e.g. CI\nenvironments).",
-      "examples": [
-        "balena support enable --device ab346f,cd457a --duration 3d",
-        "balena support enable --fleet myFleet --duration 12h",
-        "balena support disable -f myorg/myfleet"
-      ],
-      "flags": {
-        "device": {
-          "char": "d",
-          "description": "comma-separated list (no spaces) of device UUIDs",
-          "name": "device",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "fleet": {
-          "char": "f",
-          "description": "comma-separated list (no spaces) of fleet names or slugs (preferred)",
-          "name": "fleet",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "duration": {
-          "char": "t",
-          "description": "length of time to enable support for, in (h)ours or (d)ays, e.g. 12h, 2d",
-          "name": "duration",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "support",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "support",
-        "index.js"
-      ]
-    },
     "tag:list": {
       "aliases": [
         "tags"
@@ -4867,31 +4867,6 @@
         "available-drives.js"
       ]
     },
-    "whoami": {
-      "aliases": [],
-      "args": {},
-      "description": "Display account information for current user.\n\nGet the username and email address of the currently logged in user.",
-      "examples": [
-        "$ balena whoami"
-      ],
-      "flags": {},
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "whoami",
-      "pluginAlias": "balena-cli",
-      "pluginName": "balena-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": false,
-      "authenticated": true,
-      "isESM": false,
-      "relativePath": [
-        "build",
-        "commands",
-        "whoami",
-        "index.js"
-      ]
-    },
     "version": {
       "aliases": [],
       "args": {},
@@ -4935,6 +4910,31 @@
         "version",
         "index.js"
       ]
+    },
+    "whoami": {
+      "aliases": [],
+      "args": {},
+      "description": "Display account information for current user.\n\nGet the username and email address of the currently logged in user.",
+      "examples": [
+        "$ balena whoami"
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "whoami",
+      "pluginAlias": "balena-cli",
+      "pluginName": "balena-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": false,
+      "authenticated": true,
+      "isESM": false,
+      "relativePath": [
+        "build",
+        "commands",
+        "whoami",
+        "index.js"
+      ]
     }
   },
   "version": "22.5.6"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "balena-cli",
-  "version": "22.5.6-build-renovate-aws-actions-configure-aws-credentials-5-x-2944b39b3867a1dd0a575c51dd232c6fea70e9fb-1",
+  "version": "22.5.6-build-renovate-apple-actions-import-codesign-certs-3-x-a0d90954ca5b70af4b7cd88fbe1e09db72dee7fb-1",
   "description": "The official balena Command Line Interface",
   "main": "./build/app.js",
   "homepage": "https://github.com/balena-io/balena-cli",
@@ -259,6 +259,6 @@
     "balena-request": "14.0.6"
   },
   "versionist": {
-    "publishedAt": "2025-11-14T16:05:10.819Z"
+    "publishedAt": "2025-11-14T15:57:58.127Z"
   }
 }