I’ve noticed in the past few weeks that the Snapcraft Build Service is generating releases without a Github Webhook being involved. Specifically, it is overwriting edge with new releases, as if a webhook had been sent properly, bar the fact the webhook has never been triggered.
As an example, for the package
weka-james-carroll, launchpad builds #1076762 #1078956 #1099157 were all generated with no valid reason. It is not the only snap I have doing this. I did not press the request build button and Github says the last webhook sent for the associated repository was before any of these builds happened.
I can imagine this being potentially wanted behaviour, frequent rebuilds to update packages in the snap are good for maintenance, however I can also imagine that this could potentially break some workflows if edge is being overwritten with no one being involved in the process at all, such if some packages become unresolvable or parts change unexpectedly. Admittedly it’s expected that users using the edge channel might find it broken unexpectedly for whatever reason, but if the maintainers don’t even realise edge is changing without them being involved, there’s possibility for confusion.
I am leaning on thinking this is a bug but I’m curious if perhaps this is something that’s undocumented or I’ve simply not seen before. Is this something that needs escalating?
Thanks for reading!