Hi, yes my, I assume my token is for all channels, as I didn’t specify any when obtaining it.
About the issue, it seems like it’s ignoring the channel string. Otherwise I would imagine it would throw some error (either Travis or from the Snap store)
About using v2 scripts, I can try them, the syntax seem the same as what I’m using now. Also I see something strange, they define a edge: true in an example but there is no definition for such key. I’m wondering if I should then set it to false, and I just didn’t happen to know it because it’s not documented
Abot travis shutting down OSS projects, in the article you linked I only found that they set some max minutes to avoid people abusing that like to make TOR nodes and similar. Also it seems Linux VMs have otherwise no billing change. Did I miss some relevant piece?
Hi, does anyone have any recommendation for this? It would be really helpful to have an automated release to stable, so we don’t have to manually go to the store and release, that’s quite a loss of time
I think it was previously not working due to Travis not using snapcraft upload but snapcraft push, which is deprecated: bug . Thanks to @sergiusens who linked me the code, I didn’t even know it was available.
I will update once and if my pull request is accepted, to tell you if we can then use just the Travis deploy formula, without needing any custom script