[Bug]: Release not triggering for pre-release
Closed this issue · 5 comments
Contact Details
No response
What happened?
After merging the latest changing allowing to create packages for new releases, we experienced an issue where it did not trigger when creating a new release.
It was tested on a different repo where the workflow triggered for release and pre-release
as described in documentation.
Could this be a permission issue? @vaughanknight might you be able to create a test release so we can confirm please?
cc @YaSuenag
Relevant log output
There are no logs but this can show that it was not triggered https://github.com/Green-Software-Foundation/carbon-aware-sdk/actions?query=branch%3Av1.0.1
Code of Conduct
- I agree to follow this project's Code of Conduct
Thank you @vaughanknight, it looks like it is a permissions issue.
@YaSuenag, any idea which one it may be please?
See action https://github.com/Green-Software-Foundation/carbon-aware-sdk/actions/runs/5175437197/jobs/9323018801 and resulting package https://github.com/Green-Software-Foundation/carbon-aware-sdk/pkgs/container/carbon-aware-sdk/98751245?tag=v1.0.2
Speak in the morning
I'm not sure, but it may come from admin:org_hook
. https://docs.github.com/en/rest/orgs/webhooks?apiVersion=2022-11-28#scopes-and-restrictions
I guess admin:org_hook
does not granted to all of maintainers of CASDK.
I'm not sure, but it may come from
admin:org_hook
.
But other workflows are triggered - so it might not be caused by admin:org_hook
...
This issue has not had any activity in 120 days. Please review this issue and ensure it is still relevant. If no more activity is detected on this issue for the next 20 days, it will be closed automatically.
This issue has not had any activity for too long. If you believe this issue has been closed in error, please contact an administrator to re-open, or if absolutly relevant and necessary, create a new issue referencing this one.