-
Notifications
You must be signed in to change notification settings - Fork 206
Action not publishing release #74
Comments
I'm facing the same issue, does anyone how to solve this problem? |
We were using a native extension ( |
Having this issue too. @ramonbroox, what package did you replace |
One osc-something npm package. Check your package-lock.json for the |
i cannot understand what you replaced |
I was having the same issue but fixed it by pointing to the latest version of the action (as opposed to
|
I'm having this difficulty as well - my yaml is set to the following config:
The build output shows:
The builds run successfully, but there are no releases that are created in the Github repository...the same happens for osx and windows...what am I missing? |
@sators it will generate a draft release at releases page, you need to edit this draft and publish it manually. I made an Electron boilerplate with everything configured, you can check it and also check the releasing section, it shows in video this part of the draft release. |
Thank you @daltonmenezes for the swift response and links. I have looked through all of those and my config seems to match, however, I don't end up with a draft release - my releases page shows Does the action-electron-builder output have any log messages when a release is successfully created? I was seeing output at the end of the build if it was explicitly not releasing due to a tag not matching...but with |
@sators probably the action is running, but the new tag is not being detected and not triggering the draft release creation. 🤔 |
@sators here's how I made the release:
I made automation for this process by creating this CLI helper for the boileplate |
great job |
I have the same behavior. |
I was not pushing tags to the origin - See @daltonmenezes answer #74 (comment) |
Anyone who is still having this problem, in my case I solved it by giving write permission. name: Publish
on:
push:
tags: ["*"]
jobs:
publish:
if: startsWith(github.ref, 'refs/tags/v')
runs-on: ${{ matrix.os }}
permissions:
contents: write
... |
pass the |
Thanks |
Using the README action:
and tagging and pushing, no release is created. Log shows:
The text was updated successfully, but these errors were encountered: