Apologies for the cross-post here, but our original request in the “Other” category (opened 30 Dec 2025) hasn’t garnered much attention, and we’ve since realized the “repository disconnection” angle was a red herring.
We have a much clearer picture of the actual issue now. Please see the full technical context here:
This has become a significant blocker for the project. We have temporarily removed Snap installation instructions from our official documentation until this is resolved, as we don’t want to point users toward a broken experience.
We would appreciate any help or guidance the team can provide to help us get the Hugo snap back to a stable state.
I wanted to publicly express our gratitude for your assistance with this problem.
Our assumption was that builds are triggered by the webhook established when “connecting” to the repository… because that’s what the dashboard reported.
However, in our case, the builds are triggered by a setup created long ago by people who are no longer involved in our project, with the assistance of people who are no longer with Canonical.
You spent several hours of your personal time over a weekend determining how the snap is actually built and why the process failed.
This was a one-click fix that had us stumped for weeks.
In retrospect, it would have been helpful if the dashboard had some description of how the snap was actually being built. Instead, given the changes in personnel as described above, the process was opaque.
Again, thank you for your assistance; it is much appreciated.
