Skip to content
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

Advancing 0.19.0-rc3 release to status: admiral #1109

Closed
wants to merge 1 commit into from

Conversation

@submariner-bot
Copy link

🤖 I see this PR is using the local branch workflow, ignoring it on my side, have fun!

@Jaanki Jaanki requested a review from yboaron as a code owner October 18, 2024 05:02
@Jaanki Jaanki enabled auto-merge (rebase) October 18, 2024 05:02
Copy link
Contributor Author

@Jaanki Jaanki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is wrong SHA. The correct one should be 8a5ecb962986f6d57d43845e8a3bea8b172f508f as per https://github.com/submariner-io/admiral/commits/release-0.19/

@vthapar
Copy link
Contributor

vthapar commented Oct 18, 2024

Missed your comment. Are you pushing followup commit with correct sha?

Copy link

This PR/issue depends on:

components:
shipyard: 35f3468294128ce32bec0d775ff3131127dd9076
admiral: 99b5ac397a07a2256f4fa88ef99a5e65f744e149
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
admiral: 99b5ac397a07a2256f4fa88ef99a5e65f744e149
admiral: 8a5ecb962986f6d57d43845e8a3bea8b172f508f

@Jaanki Jaanki closed this Oct 18, 2024
@Jaanki
Copy link
Contributor Author

Jaanki commented Oct 18, 2024

Pushing a new PR with correct SHA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants