[v3-2-test] Work around jpype1 1.7.0 missing macOS arm64 wheels in jd…#65548
Merged
potiuk merged 1 commit intoapache:v3-2-testfrom Apr 20, 2026
Merged
[v3-2-test] Work around jpype1 1.7.0 missing macOS arm64 wheels in jd…#65548potiuk merged 1 commit intoapache:v3-2-testfrom
potiuk merged 1 commit intoapache:v3-2-testfrom
Conversation
…bc provider (apache#65532) jpype1 1.7.0 stopped shipping prebuilt macOS arm64 wheels and tries to build from source against a JDK on Apple Silicon, which breaks `uv sync` out of the box on those machines. Exclude jpype1 1.7.0 as a direct dependency of the jdbc provider, scoped to darwin-arm64 only so every other platform (including macOS x86_64) still resolves to the latest wheels. Upstream plans to restore the arm64 wheels in 1.7.1 (jpype-project/jpype#1357), after which the exclusion can be dropped. (cherry picked from commit 8ed50ae) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
1 task
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 23, 2026
…bc provider (#65532) (#65548) jpype1 1.7.0 stopped shipping prebuilt macOS arm64 wheels and tries to build from source against a JDK on Apple Silicon, which breaks `uv sync` out of the box on those machines. Exclude jpype1 1.7.0 as a direct dependency of the jdbc provider, scoped to darwin-arm64 only so every other platform (including macOS x86_64) still resolves to the latest wheels. Upstream plans to restore the arm64 wheels in 1.7.1 (jpype-project/jpype#1357), after which the exclusion can be dropped. (cherry picked from commit 8ed50ae)
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 23, 2026
…bc provider (#65532) (#65548) jpype1 1.7.0 stopped shipping prebuilt macOS arm64 wheels and tries to build from source against a JDK on Apple Silicon, which breaks `uv sync` out of the box on those machines. Exclude jpype1 1.7.0 as a direct dependency of the jdbc provider, scoped to darwin-arm64 only so every other platform (including macOS x86_64) still resolves to the latest wheels. Upstream plans to restore the arm64 wheels in 1.7.1 (jpype-project/jpype#1357), after which the exclusion can be dropped. (cherry picked from commit 8ed50ae)
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 23, 2026
…bc provider (#65532) (#65548) jpype1 1.7.0 stopped shipping prebuilt macOS arm64 wheels and tries to build from source against a JDK on Apple Silicon, which breaks `uv sync` out of the box on those machines. Exclude jpype1 1.7.0 as a direct dependency of the jdbc provider, scoped to darwin-arm64 only so every other platform (including macOS x86_64) still resolves to the latest wheels. Upstream plans to restore the arm64 wheels in 1.7.1 (jpype-project/jpype#1357), after which the exclusion can be dropped. (cherry picked from commit 8ed50ae)
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 23, 2026
…bc provider (#65532) (#65548) jpype1 1.7.0 stopped shipping prebuilt macOS arm64 wheels and tries to build from source against a JDK on Apple Silicon, which breaks `uv sync` out of the box on those machines. Exclude jpype1 1.7.0 as a direct dependency of the jdbc provider, scoped to darwin-arm64 only so every other platform (including macOS x86_64) still resolves to the latest wheels. Upstream plans to restore the arm64 wheels in 1.7.1 (jpype-project/jpype#1357), after which the exclusion can be dropped. (cherry picked from commit 8ed50ae)
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 23, 2026
…bc provider (#65532) (#65548) jpype1 1.7.0 stopped shipping prebuilt macOS arm64 wheels and tries to build from source against a JDK on Apple Silicon, which breaks `uv sync` out of the box on those machines. Exclude jpype1 1.7.0 as a direct dependency of the jdbc provider, scoped to darwin-arm64 only so every other platform (including macOS x86_64) still resolves to the latest wheels. Upstream plans to restore the arm64 wheels in 1.7.1 (jpype-project/jpype#1357), after which the exclusion can be dropped. (cherry picked from commit 8ed50ae)
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 23, 2026
…bc provider (#65532) (#65548) jpype1 1.7.0 stopped shipping prebuilt macOS arm64 wheels and tries to build from source against a JDK on Apple Silicon, which breaks `uv sync` out of the box on those machines. Exclude jpype1 1.7.0 as a direct dependency of the jdbc provider, scoped to darwin-arm64 only so every other platform (including macOS x86_64) still resolves to the latest wheels. Upstream plans to restore the arm64 wheels in 1.7.1 (jpype-project/jpype#1357), after which the exclusion can be dropped. (cherry picked from commit 8ed50ae)
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 23, 2026
…bc provider (#65532) (#65548) jpype1 1.7.0 stopped shipping prebuilt macOS arm64 wheels and tries to build from source against a JDK on Apple Silicon, which breaks `uv sync` out of the box on those machines. Exclude jpype1 1.7.0 as a direct dependency of the jdbc provider, scoped to darwin-arm64 only so every other platform (including macOS x86_64) still resolves to the latest wheels. Upstream plans to restore the arm64 wheels in 1.7.1 (jpype-project/jpype#1357), after which the exclusion can be dropped. (cherry picked from commit 8ed50ae)
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 23, 2026
…bc provider (#65532) (#65548) jpype1 1.7.0 stopped shipping prebuilt macOS arm64 wheels and tries to build from source against a JDK on Apple Silicon, which breaks `uv sync` out of the box on those machines. Exclude jpype1 1.7.0 as a direct dependency of the jdbc provider, scoped to darwin-arm64 only so every other platform (including macOS x86_64) still resolves to the latest wheels. Upstream plans to restore the arm64 wheels in 1.7.1 (jpype-project/jpype#1357), after which the exclusion can be dropped. (cherry picked from commit 8ed50ae)
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 23, 2026
…bc provider (#65532) (#65548) jpype1 1.7.0 stopped shipping prebuilt macOS arm64 wheels and tries to build from source against a JDK on Apple Silicon, which breaks `uv sync` out of the box on those machines. Exclude jpype1 1.7.0 as a direct dependency of the jdbc provider, scoped to darwin-arm64 only so every other platform (including macOS x86_64) still resolves to the latest wheels. Upstream plans to restore the arm64 wheels in 1.7.1 (jpype-project/jpype#1357), after which the exclusion can be dropped. (cherry picked from commit 8ed50ae)
vatsrahul1001
pushed a commit
to potiuk/airflow
that referenced
this pull request
Apr 23, 2026
…bc provider (apache#65532) (apache#65548) jpype1 1.7.0 stopped shipping prebuilt macOS arm64 wheels and tries to build from source against a JDK on Apple Silicon, which breaks `uv sync` out of the box on those machines. Exclude jpype1 1.7.0 as a direct dependency of the jdbc provider, scoped to darwin-arm64 only so every other platform (including macOS x86_64) still resolves to the latest wheels. Upstream plans to restore the arm64 wheels in 1.7.1 (jpype-project/jpype#1357), after which the exclusion can be dropped. (cherry picked from commit 8ed50ae)
vatsrahul1001
pushed a commit
to potiuk/airflow
that referenced
this pull request
Apr 23, 2026
…bc provider (apache#65532) (apache#65548) jpype1 1.7.0 stopped shipping prebuilt macOS arm64 wheels and tries to build from source against a JDK on Apple Silicon, which breaks `uv sync` out of the box on those machines. Exclude jpype1 1.7.0 as a direct dependency of the jdbc provider, scoped to darwin-arm64 only so every other platform (including macOS x86_64) still resolves to the latest wheels. Upstream plans to restore the arm64 wheels in 1.7.1 (jpype-project/jpype#1357), after which the exclusion can be dropped. (cherry picked from commit 8ed50ae)
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
1 participant
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.
…bc provider (#65532)
jpype1 1.7.0 stopped shipping prebuilt macOS arm64 wheels and tries to build from source against a JDK on Apple Silicon, which breaks
uv syncout of the box on those machines. Exclude jpype1 1.7.0 as a direct dependency of the jdbc provider, scoped to darwin-arm64 only so every other platform (including macOS x86_64) still resolves to the latest wheels. Upstream plans to restore the arm64 wheels in 1.7.1 (jpype-project/jpype#1357), after which the exclusion can be dropped.(cherry picked from commit 8ed50ae)
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.