Jefffrey commented on PR #11692: URL: https://github.com/apache/arrow-rs/pull/11692#issuecomment-6352029244
> > I would mark this as a major API change because pyo3 specifically can only have a single version in your cargo build. Because of that, anyone who uses this would have to update to 0.30. > > Should the bump then be called out in the changelog as a breaking change? I see previous entries are only mentioned in the generic `Merged pull requests` section. no action needs to be done on this PR, we handle changelog at release time. it just means this PR wont go in until 61.0.0 is the next release, which at this rate is likely to be december -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
