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

release 0.11.1 #493

Merged
merged 1 commit into from
Mar 29, 2024
Merged

release 0.11.1 #493

merged 1 commit into from
Mar 29, 2024

Conversation

prednaz
Copy link
Member

@prednaz prednaz commented Mar 29, 2024

patch release to trigger publish-to-bcr again after #491

@prednaz prednaz requested a review from cgrindel March 29, 2024 17:33
@prednaz prednaz marked this pull request as ready for review March 29, 2024 17:35
@prednaz prednaz requested a review from benradf as a code owner March 29, 2024 17:35
@prednaz prednaz added the merge-queue merge on green CI label Mar 29, 2024
@mergify mergify bot merged commit 126e9f6 into master Mar 29, 2024
15 checks passed
@mergify mergify bot deleted the release-0.11.1 branch March 29, 2024 18:47
@mergify mergify bot removed the merge-queue merge on green CI label Mar 29, 2024
@avdv
Copy link
Member

avdv commented Apr 2, 2024

I assume it failed again, since our release workflow is still broken because of cgrindel/gha_join_jobs#52

To workaround, I'll upload the tarballs manually and create a PR to the BCR.

Oh, everything is just fine - the BCR PR is already merged. Sorry for the noise!

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

Successfully merging this pull request may close these issues.

3 participants