Skip to content

release: 0.24.0 #4959

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

Merged
merged 1 commit into from
Mar 9, 2025
Merged

release: 0.24.0 #4959

merged 1 commit into from
Mar 9, 2025

Conversation

davidhewitt
Copy link
Member

I think it's time we shipped a release.

Thank you to @Icxolu, @ngoldbaum and @bschoenmaeckers in particular, who have done a huge amount of the work and support in heading towards this release while I've been busy. I'm hopeful that I can be much more active in the coming months so we can make further progress on some of the things we know we want to improve in the releases to follow 0.24.

I'd like to ship ASAP; I think there's just a couple of PRs I would like to get merged before this is finalised and I prepare the CHANGELOG:

Please ping if there's anything else you think must be included in the release. Once those PRs are in, I will do a final rebase & prep here and leave just a couple days for cooling off.

@davidhewitt davidhewitt marked this pull request as draft March 7, 2025 09:27
@bschoenmaeckers
Copy link
Member

I'm investigating the jiff failure in the CI. It looks like jiff 0.2.2 broke something.

@BurntSushi
Copy link

Your CI failures might have found a legit bug in the latest Jiff release. I'll take a closer look too.

@bschoenmaeckers
Copy link
Member

Your CI failures might have found a legit bug in the latest Jiff release. I'll take a closer look too.

I've created a issue in the jiff repo with a minimal example.
BurntSushi/jiff#290

@ahlinc
Copy link
Contributor

ahlinc commented Mar 7, 2025

@davidhewitt Could you consider to include this #4951 PR too?

@davidhewitt davidhewitt marked this pull request as ready for review March 8, 2025 08:29
@davidhewitt
Copy link
Member Author

With the above PRs merged, I have prepped the release notes and plan to ship this tomorrow evening.

@ahlinc sorry for not replying to your PR yet. Thank you for working on __init__ support; it's an important feature and I would love to get it merged, there are also a few other similar PRs with awesome features which are long overdue reviews from me, and I want to help review and merge these in the coming days. But I think for all of these, better to allow some time to iterate / review these and get them in good shape for 0.25 rather than rush them. This 0.24 release already contains ~4 months of features and is very due for release!

@arielb1
Copy link
Contributor

arielb1 commented Mar 9, 2025

Do you think we should merge #4874 ?

@davidhewitt
Copy link
Member Author

Done, will do a last rebase here 👍

Co-authored-by: Icxolu <[email protected]>
@davidhewitt davidhewitt enabled auto-merge March 9, 2025 21:49
@davidhewitt davidhewitt added this pull request to the merge queue Mar 9, 2025
Merged via the queue into main with commit 059e249 Mar 9, 2025
48 checks passed
@davidhewitt davidhewitt deleted the release-0.24.0 branch March 9, 2025 23:10
@messense
Copy link
Member

docs is broken, it returns Page not found currently: https://pyo3.rs/v0.24.0/

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.

7 participants