The snapcraft 7 command options differ depending on the snap's base. The command help shows options that work only if the snap base is core22. This is particularly an issue in reusable CI workflows when the snap base isn't fixed. Snapcraft 7 + core22 doesn't print the build errors to standard output/err but rather to a file which isn't always accessible (e.g. when building snaps on Launchpad). Setting the verbose flag will work when core22 is used but results in an error and non-zero exit code otherwise. $ snapcraft --version snapcraft 7.0.8 $ snapcraft --help Usage:     snapcraft [help] <command> Summary: Package, distribute, and update snaps for Linux and IoT Global options:                        -h, --help: Show this help message and exit                     -v, --verbose: Show debug information and be more                                     verbose                       -q, --quiet: Only show warnings and errors, not                                     progress                       -t, --trace: Show all information needed to trace                                     internal behaviour                     -V, --version: Show the application version and                                     exit ... $ snapcraft --verbose ... Try 'snapcraft -h' for help. Error: No such option: --verbose Did you mean --version? $ yq ".base" snap/snapcraft.yaml core20