-
Notifications
You must be signed in to change notification settings - Fork 884
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
[54.2.0_maintenance] Bump arrow version to 54.2.1 #7207
[54.2.0_maintenance] Bump arrow version to 54.2.1 #7207
Conversation
cc @alamb, I'm open to change this release to |
Thank you for this, i think we should instead backport the chrono fix onto the last release instead of releasing from main. Less risk that way if we're going to shortcut the release process |
Looks good to me. Would you like to create a branch from |
Thank you for this. |
Signed-off-by: Xuanwo <[email protected]>
8e2f915
to
8cb9caf
Compare
This PR is ready to go. |
I will plan to do the release / public discussion / writeup about this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signed-off-by: Xuanwo <[email protected]>
Signed-off-by: Xuanwo <[email protected]> Co-authored-by: Xuanwo <[email protected]>
Which issue does this PR close?
54.3.0
(Mar 2025) #7107Rationale for this change
Get a patch release so we can avoid breaking after new chrono release.
What changes are included in this PR?
Version and changelog bumps.
Are there any user-facing changes?
None
I request that this release be made under emergency circumstances, allowing it to be released as soon as possible after gathering three +1 binding votes, without waiting for three days.