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

0.12.0 #734

Merged
merged 1 commit into from
Mar 30, 2024
Merged

0.12.0 #734

merged 1 commit into from
Mar 30, 2024

Conversation

cottsay
Copy link
Member

@cottsay cottsay commented Mar 29, 2024

I've done zero curation to the CHANGELOG entries, just dumped the git log --oneline and fixed up the URLs. Please suggest any fixups or perspective omissions.

Blocked on #732 and #733

@cottsay cottsay self-assigned this Mar 29, 2024
Copy link
Contributor

@nuclearsandwich nuclearsandwich left a comment

Choose a reason for hiding this comment

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

I have proposed an additional PR to try and scoot into the release (hopefully avoiding a regression in a released version of bloom along the way). But if it has problems I don't think we are required to block the release for it.

@cottsay cottsay marked this pull request as ready for review March 29, 2024 22:16
CHANGELOG.rst Show resolved Hide resolved
@cottsay cottsay merged commit 9647e9e into master Mar 30, 2024
15 checks passed
@cottsay cottsay deleted the release/0.12.0 branch March 30, 2024 05:01
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.

2 participants