-
Notifications
You must be signed in to change notification settings - Fork 66
chore: move goreleaser job to release workflow #878
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
3050b9e
to
9e328e1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACKe
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still need the independent goreleaser workflow for the manually created releases?
@filippos47 Yes I do think we need it. gorelease is still needed in case we create the release without using the workflow |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
When a release is created using the release workflow, it doesn't trigger the gorelease workflow due to the limitation with
github.token
(ref).This PR moves the goreleaser job into the release workflow, allowing it to be executed once the release is created