raulcd commented on issue #36065: URL: https://github.com/apache/arrow/issues/36065#issuecomment-1591450665
This is weird indeed. The release branch contained the update to the `CMakeLists.txt` and the `setup.py` as seen here: https://github.com/apache/arrow/commit/6af660f48472b8b45a5e01b7136b9b040b185eb1#diff-005a07ca82fb46b215f58a3a8f4d6d6cc6ca088ade44e8f15cc2e6a51d1da6f4 That commit (6af660f48472b8b45a5e01b7136b9b040b185eb1) is also on the tag: https://github.com/apache/arrow/releases/tag/apache-arrow-12.0.1 It does seem that the binaries submitted used the following commit though: eb89c633abccd463f8472eaed37aa12c5f210a27 That commit was the last one on the maintenance branch before merging the version updates. I extracted that commit from the wheels job here: https://github.com/ursacomputing/crossbow/actions/runs/5201602383/workflow#L52 Which are the jobs on the PR for the binary submission: https://github.com/apache/arrow/pull/35967 The arrow branch used based on the script should be the tag based on: ``` release_tag="apache-arrow-${version}" : ${ARROW_BRANCH:=$release_tag} ``` but it does seem it did not use that one based on the hash on the comment: https://github.com/apache/arrow/pull/35967#issuecomment-1581005613 @kou any idea what might have happened? -- 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]
