db reset --version is shadowed by the global --version flag in 2.101.0

[ahmed-fawzy99]

Describe the bug

supabase db reset --version <timestamp> does not reset to the given migration. It prints the CLI version string and exits without doing anything. The local --version <string> flag on db reset is shadowed by the global --version flag that shows version info.

This looks like a regression. The space form is the documented syntax and worked in older releases. Closed issue #3723 shows --version 0001 working on v2.26.8.

To reproduce

$ supabase db reset --version
2.101.0

$ supabase db reset --version 20230101000000
2.101.0

No reset happens in either case.

Expected behavior

The database should reset up to and including the specified migration version, matching the documented example supabase db reset --version 20230101000000.

System information

• CLI version: 2.101.0 (latest stable)
• OS: Linux

[7ttp]

hi @ahmed-fawzy99 thanks for reporting!! 💚
can confirm it was reproducible

have pushed up a fix, will likely get reviewed in few hrs from now :D