🐛 [Bug]: Command error tells me to use the --verbose flag but I am already using it

[angelikatyborska]

Package

storyblok (CLI)

Bug Description

I tried to push stories from space A to space B without first pulling them, and I got an error - that's good 🙂. But the error included the phrase:
ℹ For more information about the error, run the command with the `--verbose` flag

I was already using the --verbose flag, and seeing this phrase in the error makes me wonder: is this just a matter of hardcoded error messages, or did the CLI really did not pass the flag along and I am actually not seeing all the error details? See "Error Logs" below for the full command output.

Steps to Reproduce

1. Do not pull stories from "space A"
2. Try to run the push stories command from "space A" to "space B" with the --verbose flag

Expected Behavior

When using the --verbose flag, I expect to see all the available debug and error logs, and I don't expect to be told to use the --verbose flag.

Actual Behavior

I am not sure if I see all the available debug and error logs, and I am told to use the --verbose flag.

Code Sample

Environment

System:
    OS: macOS 26.2
    CPU: (11) arm64 Apple M3 Pro
    Memory: 67.73 MB / 18.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.14.0 - /Users/angelikacathor/.asdf/installs/nodejs/22.14.0/bin/node
    npm: 11.2.0 - /Users/angelikacathor/.asdf/plugins/nodejs/shims/npm
    pnpm: 10.21.0 - /Users/angelikacathor/.asdf/installs/nodejs/22.14.0/bin/pnpm
    bun: 1.2.15 - /Users/angelikacathor/.bun/bin/bun
  Browsers:
    Brave Browser: 141.1.83.118
    Chrome: 144.0.7559.133
    Edge: 144.0.3719.104
    Firefox Developer Edition: 148.0
    Safari: 26.2
  npmPackages:
    @storyblok/astro: ^6.2.0 => 6.2.0 
    @storyblok/js: 3.5.0 => 3.5.0 
    astro: ^5.16.11 => 5.16.11 
    storyblok: ^4.14.1 => 4.14.1

Error Logs

$ ./node_modules/.bin/storyblok stories push --from 123 --space 456 --verbose


  Storyblok CLI  


 Stories  Pushing stories...


 Error 

▲ error Failed to read/parse file: 
▲ error The file requested was not found 

ℹ For more information about the error, run the command with the `--verbose` flag


 Creating Stories...    [■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■] 100% | 0s | 0/0 processed
 Processing Stories...  [■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■] 100% | 0s | 0/0 processed
 Updating Stories...    [■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■] 100% | 0s | 0/0 processed
ℹ Push results: 0 stories pushed, 0 stories failed

  Creating stories: 0/0 succeeded, 0 failed.
  Processing stories: 0/0 succeeded, 0 failed.
  Updating stories: 0/0 succeeded, 0 failed.

Additional Context

No response