CLI flags should not be case-sensitive (`apiops -v` fails, `-V` works)

[petehauge]

Command that triggered the bug

apiops -v

Expected behavior

Both apiops -v and apiops -V should print the installed CLI version. Users commonly expect short flags to be case-insensitive, and -v is the conventional lowercase form for "version" across most CLIs.

Actual behavior

Only apiops -V prints the version. apiops -v fails / is not recognized as the version flag. This is inconsistent and surprising for users.

Ideally, command-line short flags in general should not be case-sensitive — or at minimum, -v should be aliased to -V (and --version) for the version output.

apiops CLI version

0.4.0-alpha.1

Environment details

• OS: Windows 11
• Shell: PowerShell 7.6.3
• Node.js: v24.0.1
• npm: 11.11.0

CI/CD environment

N/A (running locally)

Is this bug blocking you?

No

[github-actions]

🏷️ Triage Recommendation

Type: type:bug (already applied)
Effort: effort:S — one-line change in src/cli/index.ts
Domain: CLI wiring (src/cli/index.ts)
Confidence: high (92%)
Uncertainty: none — clear reproduction, isolated to a single file, root cause is obvious

Reasoning

Commander.js defaults the version flag to -V, --version; -v is simply not registered, so it falls through to the "unknown command" handler. The fix is to pass a custom flags string to .version() that includes both short forms: .version(packageJson.version, '-v, -V, --version', 'Print version').

Recommended next steps

• Confirm that no existing option or subcommand in the CLI already uses -v (quick grep — looks clean).
• Apply the one-line change in src/cli/index.ts and update any snapshot/help-text tests.
• Consider whether other convention flags (e.g. -h alongside --help) warrant the same treatment, though that is out of scope for this issue.

Generated by Contract test: verify context separation for #224 · 23.2 AIC · ⌖ 6.75 AIC · ⊞ 6.5K · ◷

[github-actions]

⚠️ Stale issue notice — This issue has had no activity for 30 day(s).

It will be automatically closed after 60 days of inactivity.

To keep this issue open:

• Leave a comment describing the current status, or
• Remove the stale label.

This notice was posted automatically by the stale issue workflow.