Work around jpype1 1.7.0 missing macOS arm64 wheels in jdbc provider#65532
Merged
potiuk merged 1 commit intoapache:mainfrom Apr 20, 2026
Merged
Work around jpype1 1.7.0 missing macOS arm64 wheels in jdbc provider#65532potiuk merged 1 commit intoapache:mainfrom
potiuk merged 1 commit intoapache:mainfrom
Conversation
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.
potiuk
added
the
backport-to-v3-2-test
eladkal
approved these changes
Apr 20, 2026
Contributor
Backport failed to create: v3-2-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 8ed50ae v3-2-testThis should apply the commit to the v3-2-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Apr 20, 2026
…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
Member
Author
|
Backport in #65548 |
potiuk
added a commit
that referenced
this pull request
Apr 20, 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)
jscheffl
reviewed
Apr 20, 2026
| # wheels in 1.7.1 (see https://github.com/jpype-project/jpype/issues/1357). Other | ||
| # platforms (including macOS x86_64) still get all published versions. | ||
| "jpype1>=1.4.0,!=1.7.0; sys_platform == 'darwin' and platform_machine == 'arm64'", | ||
| "jpype1>=1.4.0; sys_platform != 'darwin' or platform_machine != 'arm64'", |
Contributor
There was a problem hiding this comment.
FYI also in parallel to Slack: Also fails now on Python 3.11+3.12+3.13+3.14, only 3.10 seem to be working
1 task
59 tasks
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
3 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.
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 for contributors on that hardware.Exclude jpype1 1.7.0 as a direct dependency of the jdbc provider, scoped to
sys_platform == 'darwin' and platform_machine == 'arm64'only, so every other platform (including macOS x86_64) still resolves to the latest wheels.jaydebeapistays as the direct runtime dependency — the jpype1 pin is purely to steer the transitive resolution on Apple Silicon.Upstream is planning to restore the arm64 wheels in 1.7.1 (see jpype-project/jpype#1357), after which the
!=1.7.0marker can be dropped.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (claude-opus-4-7) following the guidelines