Closed stamoun closed 3 years ago
I removed a few things that were probably causing this (the publish
part of the build, the args
in the yaml).
I'll be using the tag to trigger a build and create a draft release. I think I was overthinking the process :)
Actually, it still fails miserably, I updated the original post with the latest log and release.yml
(package.json
no longer contains a publish
section).
Am I only missing the secrets.snapcraft_token
?
Do I need to have that? Can't I just build a .snap
without having to log into a 3rd party?
@stamoun I ran into this issue too, I think we need to follow the instructions here https://github.com/samuelmeuli/action-electron-builder#snapcraft
I bypassed the snap store by using args: "-c.snap.publish=github -p always"
in the workflow file as well as the following in the build
element of package.json
:
"build": {
...
"publish": [
{
"provider": "github",
"releaseType": "draft"
}
]
...
With these two modifications, I was able to publish the snap without hitting the snap store so this is no longer an issue for me.
I'm trying to get automated release update to publish binaries and so far Linux is failing (Mac and Windows seem ok, albeit unsigned binaries).
The builder fails with the following (full log here)
Here's my workflow action file:
From what I can gather from the log, the
snap
file is created but there is an issue uploading it to GitHub releases?