[CI] Bump cargo-zigbuild for aarch64 Linux - #787
Merged
Merged
Conversation
Signed-off-by: teodordelibasic-db <teodor.delibasic@databricks.com>
teodordelibasic-db
requested review from
a team,
danilonajkov-db,
elenagaljak-db and
nikolaobradovic-db
August 26, 2026 09:49
Signed-off-by: teodordelibasic-db <teodor.delibasic@databricks.com>
elenagaljak-db
approved these changes
Aug 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes are proposed in this pull request?
Bump
cargo-zigbuildfrom 0.19.8 to 0.23.0 in the JNI, FFI, Go, C++, and .NET release builders.Current
stablerustc (1.98) passes-Wl,--fix-cortex-a53-843419when linking aarch64 Linux. Zig 0.13 rejects that GNU ld flag, socargo zigbuildfails onlinux-aarch64andlinux-musl-aarch64. cargo-zigbuild 0.23.0 drops that argument before invoking zig. Zig itself stays at 0.13.0.0.23.2 also has the filter, but JFrog's 7-day cooldown blocks it (the crate is two days old). 0.23.0 is from June and already filters the flag.
How is this tested?
JNI builder dispatched on this branch. 0.19.8 failed aarch64 with
unsupported linker arg: --fix-cortex-a53-843419. 0.23.2 failed all zigbuild jobs with JFrog 403 on crate download.