Pin python-build 20260630 (armeabi-v7a for 3.13/3.14); serious_python 4.2.0 - #6628
Merged
Conversation
… 4.2.0 python-build 20260630 publishes armeabi-v7a (32-bit ARM) for Python 3.13 and 3.14, not just 3.12 (built with dart_bridge 1.4.1). Bump the pinned release date so the manifest-driven ABI set picks them up automatically, and bump the build template's serious_python pin to 4.2.0. - python_versions.py: PYTHON_BUILD_RELEASE_DATE 20260618 -> 20260630; refresh the now-stale "only 3.12 carries armeabi-v7a" comment. - build.gradle.kts template: collapse the dead per-version abiFilters fallback (target_arch is always set from the manifest) and drop the PEP 738 comment. - pubspec.yaml template: serious_python 4.1.1 -> 4.2.0. - CHANGELOG: correct the "3.13+ drops armeabi-v7a" note; Pyodide 3.14 314.0.1.
Deploying flet-website-v2 with
|
| Latest commit: |
9f07629
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b52824a3.flet-website-v2.pages.dev |
| Branch Preview URL: | https://armeabi-v7a-3-13-3-14.flet-website-v2.pages.dev |
macos-integration-tests, flet-test and flet-build-test only need to run on branch/PR pushes; on release tag pushes they're redundant (and can fail). Add `tags-ignore: ['**']` to each push trigger so tags no longer fire them.
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
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
python-build
20260630publishesarmeabi-v7a(32-bit ARM) runtimes for Python 3.13 and 3.14 (not just 3.12), built withdart_bridge1.4.1. This bumps flet's pinned python-build release so the manifest-driven Android ABI set picks them up automatically, and moves theflet buildtemplate toserious_python4.2.0 (released).Changes
python_versions.py:PYTHON_BUILD_RELEASE_DATE20260618→20260630; refresh the now-stale "only 3.12 carries armeabi-v7a" comment.PythonRelease.android_abisis read straight from the manifest, so 3.13/3.14 gainarmeabi-v7awith no table edit.abiFiltersfallback (build_base.pyalways setstarget_archfrom the manifest) into a single default and drop the PEP 738 comment.pubspec.yamltemplate:serious_python4.1.1→4.2.0.314.0.1.Verification
get_supported_python_versions()reportsarmeabi-v7afor 3.12/3.13/3.14 against the real20260630manifest.pytest tests/test_python_versions.pypasses (10/10).Companion releases already shipped: dart-bridge
v1.4.1, python-build20260630, serious_python4.2.0.Summary by Sourcery
Pin the CLI to the latest python-build manifest and update Android and Dart templates so new ABI and runtime support are picked up automatically.
Enhancements:
Documentation: