Tags: apache/arrow-rs
Tags
Update version to `56.2.0`, add changelog (#8372) # Which issue does this PR close? We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. - part of #7836 # Rationale for this change Prepare for the next release # What changes are included in this PR? 1. Update changelog (see rendered preview here: https://github.com/alamb/arrow-rs/blob/alamb/prepare_for_56.2.0/CHANGELOG.md) 2. Update version # Are these changes tested? By CI # Are there any user-facing changes?
Update version to `56.2.0`, add changelog (#8372) # Which issue does this PR close? We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. - part of #7836 # Rationale for this change Prepare for the next release # What changes are included in this PR? 1. Update changelog (see rendered preview here: https://github.com/alamb/arrow-rs/blob/alamb/prepare_for_56.2.0/CHANGELOG.md) 2. Update version # Are these changes tested? By CI # Are there any user-facing changes?
Prepare for `56.1.0` release (#8202) # Which issue does this PR close? - Part of #7837 # Rationale for this change Prepare for release # What changes are included in this PR? 1. Changelog. Preview here: https://github.com/alamb/arrow-rs/blob/alamb/prepare_for_56.1.0/CHANGELOG.md 2. Update version to `56.1.0`
Prepare for `56.1.0` release (#8202) # Which issue does this PR close? - Part of #7837 # Rationale for this change Prepare for release # What changes are included in this PR? 1. Changelog. Preview here: https://github.com/alamb/arrow-rs/blob/alamb/prepare_for_56.1.0/CHANGELOG.md 2. Update version to `56.1.0`
Fix doc test in avro-arrow (#8020) # Which issue does this PR close? - part of #7395 - Closes #8018 # Rationale for this change Fix a bug I found while testing the RC # What changes are included in this PR? Check the ARROW_TESTING directory first before looking at the local path # Are these changes tested? Yes, by CI and I tested it manually # Are there any user-facing changes? No
Fix doc test in avro-arrow (#8020) # Which issue does this PR close? - part of #7395 - Closes #8018 # Rationale for this change Fix a bug I found while testing the RC # What changes are included in this PR? Check the ARROW_TESTING directory first before looking at the local path # Are these changes tested? Yes, by CI and I tested it manually # Are there any user-facing changes? No
Prepare for `56.0.0` release: Update version and `CHANGELOG.md` (#8014) # Which issue does this PR close? - part of #7395 # Rationale for this change Keep the code flowing # What changes are included in this PR? 1. Update CHANGELOG. See rendered version here: https://github.com/alamb/arrow-rs/blob/alamb/prepare_56.0.0/CHANGELOG.md 2. Update version to `56.0.0` # Are these changes tested? N/A # Are there any user-facing changes? Yes
[55_maintenance] Fix verify-release-candidate.sh by skipping `arrow-p… …yarrow` and `parquet-variant` (#7745) Note this targets a release branch, not main I have a different proposed fix for `main`: - #7742 I will also make a fix for parquet-variant test failures # Which issue does this PR close? - Related to #7394 - Related to #7736 - Related to #7746 # Rationale for this change `cargo test --all` requires python and pyarrow installed, where it did not in previous versions of arrow due to breaking out `arrow-pyarrow` into its own crate in - #7694 Also the new `parquet-variant` crate tests fail as part of the verification script too -- see ttps://github.com//issues/7746 In order to get a script that can automatically verify a release candidate, let's ignore this new module for now. More details - #7736 - #7742 Note that the arrow-pyarrow tests do run as part of CI and succeed on this branch # What changes are included in this PR? 1. Exclude running the `arrow-pyarrow` and `parquet-variant` tests as part of `verify-release-acndidate` # Testing I verified locally that `./dev/release/verify-release-candidate.sh 55.2.0 1` passes with this script # Are there any user-facing changes? No this is a development process only change
PreviousNext