-
Notifications
You must be signed in to change notification settings - Fork 17
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
Release of version 1.3.1 #599
Conversation
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.
This is an auto-approve of an auto-PR.
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: sefkhet-abwy[bot] The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
1 similar comment
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: sefkhet-abwy[bot] The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@harshad16 wrt your demo on last sprint demo session, can this even 'issue clue' trigger a rebuild of the thoth-toolbox container image? |
@goern i think we need something like a post trigger, as the current sync pipeline does synchronous release, which in this case would be a race.
we would need a post-trigger, which triggers a release of thoth-toolbox when release of thamos is completed. |
Hey, @fridex!
Opening this PR to fix the last release.
Related: #598