I reported this on the call for testing snapcraft 7 (https://forum.snapcraft.io/t/call-for-testing-snapcraft-7/30201/43). Reporting it here again so that it is not forgotten. I have my configure and install hooks as binary executables placed under `$SNAPCRAFT_PART_INSTALL/snap/hooks/` during the part's build. When using snapcraft 7.0.3, the resulting snap doesn't run the install / configure hooks and `snap set` fails due to the lack of a configure hook. Source code: https://github.com/farshidtz/edgex-device-usb-camera/blob/4df80eefb8af4e7f598d31ac79e90a8636e25008/snap/snapcraft.yaml#L52-L60) Inside the package, the hooks are under `snap/hooks` as they used to be, but there are no longer any scripts calling them from `meta/hooks/configure` and `meta/hooks/configure` . Package built with snapcraft 7.0.3: ``` $ tree squashfs-root_7/snap/hooks/ squashfs-root_7/snap/hooks/ ├── configure └── install 0 directories, 2 files $ tree squashfs-root_7/meta/ squashfs-root_7/meta/ ├── gui │ └── icon.png └── snap.yaml 1 directory, 2 files ``` Package built with snapcraft 6: ``` $ tree squashfs-root_6/snap/hooks/ squashfs-root_6/snap/hooks/ ├── configure └── install 0 directories, 2 files $ tree squashfs-root_6/meta/ squashfs-root_6/meta/ ├── gui │ └── icon.png ├── hooks │ ├── configure │ └── install └── snap.yaml 2 directories, 4 files $ cat squashfs-root_6/meta/hooks/configure #!/bin/sh PATH="$SNAP/usr/sbin:$SNAP/usr/bin:$SNAP/sbin:$SNAP/bin${PATH:+:$PATH}" LD_LIBRARY_PATH="${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}$SNAP/usr/lib:$SNAP/usr/lib/x86_64-linux-gnu" export LD_LIBRARY_PATH="$SNAP_LIBRARY_PATH${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}" exec "$SNAP/snap/hooks/configure" "$@" ```