Closed supersu-man closed 1 year ago
I'm also having this issue. Gonna leave the comment in the hopes someone fixes it.
I'm also having this issue. Gonna leave the comment in the hopes someone fixes it.
Did you try creating a release before using this action ? or maybe tried for a workaround?
I'm also having this issue. Gonna leave the comment in the hopes someone fixes it.
Did you try creating a release before using this action ? or maybe tried for a workaround?
I tried creating a release, as it seemed the only workaround, but it didn't work. I didn't try any other workaround, though.
I'm also having this issue. Gonna leave the comment in the hopes someone fixes it.
Did you try creating a release before using this action ? or maybe tried for a workaround?
I tried creating a release, as it seemed the only workaround, but it didn't work. I didn't try any other workaround, though.
The action is not working anymore, I've made a test repo and been testing by making changes to .yml file but no luck.
The GITHUB_TOKEN
that's automatically generated for the workflow doesn't have permission to create the release, hence the 403.
The easiest solution is to allow Read and write permissions
in the repo's Actions settings:
Go to: https://github.com/__REPO_OWNER__/__REPO_NAME__/settings/actions (Your Repo -> Settings -> Actions -> General)
Update the permission under Workflow permissions
, then save.
More info: https://docs.github.com/en/actions/security-guides/automatic-token-authentication
The
GITHUB_TOKEN
that's automatically generated for the workflow doesn't have permission to create the release, hence the 403.The easiest solution is to allow
Read and write permissions
in the repo's Actions settings:
- Go to: https://github.com/__REPO_OWNER__/__REPO_NAME__/settings/actions (Your Repo -> Settings -> Actions -> General)
- Update the permission under
Workflow permissions
, then save.More info: https://docs.github.com/en/actions/security-guides/automatic-token-authentication
I can attest that this method is currently functional, and may just be the workaround for those who are waiting for a change in the action itself.
I can attest that this method is currently functional, and may just be the workaround for those who are waiting for a change in the action itself.
@Gilvan-Araujo I wouldn't call it a "workaround". This isn't an issue with the the action itself. Actions shouldn't be able to set what permissions they have, so there's nothing to fix here.
Maybe it should be better documented now though, because for new repos, the permissions for the auto-generated GITHUB_TOKEN are all read-only now.
So people can either use the solution I posted above, use a Personal Access Token, or set the permissions key in their workflow file.
Please, add documentation about this in the README.