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
chore(release): use robot for deploys #158
Conversation
fe5ee86
to
47fd071
Compare
846aae0
to
97cd5bd
Compare
/lgtm |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: benluddy, dinhxuanvu, ecordell 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 |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
@ecordell this commit complete breaks the builds of 4.4+ on other architectures. Please revert immediately. |
Description of the change:
This switches the api key to use
of-deploy-bot
's credentials, which currently only has write on this repo (versus my credentials which have access to many and which I will now rotate).This also shuffles the release artifacts a bit so that they don't conflict when updating a release. See this test release made from this branch: https://github.com/operator-framework/operator-registry/releases/tag/v0.0.7-test
Motivation for the change:
Reviewer Checklist
/docs