You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add serious_python:main version [--json] + CI vars from registry
The Dart `_pythonReleases` registry is the source of truth for the
Python version matrix, but until now CI (and any other external
consumer) needed a hand-maintained lookup table to derive the full
patch version + python-build release date from the short
SERIOUS_PYTHON_VERSION. Last CI run failed exactly because the new
SERIOUS_PYTHON_FULL_VERSION / SERIOUS_PYTHON_BUILD_DATE env vars were
unset in CI, the plugin scripts fell back to their 3.14.6/20260611
defaults, and Linux's ninja then complained that the 3.12 tarball was
missing libpython3.14.so.1.0.
New `version` subcommand emits the registry as either a human-readable
summary or `--json` (machine-readable). Self-version comes from
pubspec.yaml looked up via `package_config` (no Dart constant to keep
in sync). Registry rows are sorted descending in the text output to
match `flet --version` ordering.
`_pythonReleases` and `_PythonRelease` promoted to `pythonReleases` /
`PythonRelease` so the new file can reference them. Internal callers
in `package_command.dart` updated to match.
CI: new composite action `.github/actions/resolve-python-vars` runs
`dart run serious_python:main version --json` + `jq` to write
SERIOUS_PYTHON_FULL_VERSION and SERIOUS_PYTHON_BUILD_DATE into
`$GITHUB_ENV`. Inserted as a `Resolve Python version vars` step right
after `Setup Flutter` in all 15 test jobs (publish job left untouched).
Future Python registry bumps need no CI changes.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments