bug: `apps:bundles:create` command should accept empty string for --channel option

[matias-miranda]

Version

3.2.1

Current behavior

When I execute the CLI it asks me for a channel, then I select No, then it successfully creates the bundle without a channel:

so I was trying to do the same but running the CLI from a custom .sh script locally on my machine. I tried setting an empty --channel like this:

npx @capawesome/cli apps:bundles:create --app-id xxx --channel ""

but then I get ERROR Invalid input: expected string, received boolean

Expected behavior

It should accept an empty string as the --channel option, because it's optional to create a bundle.

This fix allows me to workaround it, but it doesn't fully fit the scenario I described, where I execute it locally, instead of on some of the providers for which isCi is true from std-env lib

Steps to reproduce

1. When running locally (none of the providers detected by std-env lib)
2. Run npx @capawesome/cli apps:bundles:create --app-id xxx --channel ""
3. See the error Invalid input: expected string, received boolean

Other information

No response

Doctor

 ╭───────────────────────────╮
 │                           │
 │  NodeJS version: 22.14.0  │
 │  NPM version: 11.3.0      │
 │  CLI version: 3.2.1       │
 │  OS: macOS 26.0 (macOS)   │
 │                           │
 ╰───────────────────────────╯

Before submitting

• I have read and followed the bug report guidelines.
• I have attached links to possibly related issues and discussions.
• I understand that incomplete issues (e.g. without reproduction) are closed.

[robingenz]

Thank you for creating this issue. Even though the error message is misleading, the CLI is behaving correctly. An empty channel name is an invalid value. Instead, you should simply not use the parameter. I am therefore closing this issue.

[matias-miranda]

@robingenz if i don't specify --channel parameter, the command requires user interaction. so if i want to create a bundle without a channel and without user intervention it's simply not possible unless i'm in a CI env.
it's still contradictory in my opinion, because providing an empty channel parameter is equivalent to answering "NO" to the question of whether you want to deploy to a specific channel

[robingenz]

@matias-miranda Alright, got it. This dev build should work for you:

npm i @capawesome/cli@3.2.1-dev.fa8dc69.1759001719

It checks for an interactive terminal before prompting. Please let me know if it works.

EDIT: You still have to omit the parameter.

[matias-miranda]

that's great @robingenz
thanks!

[robingenz]

@matias-miranda Awesome, thank you for your help.