20260614

Add manifest.json as the runtime source of truth (#15)

* Add manifest.json as the runtime source of truth

manifest.json now drives the CI build matrix (the setup job reads
[.pythons[].full_version] from it) and is published as a release asset
with the release date injected, so serious_python and flet consume a
single consistent version set (CPython + pyodide + dart_bridge) keyed by
release date instead of hand-mirroring versions.

* Bump actions/checkout to v6 in workflows

Update .github/workflows/build-python.yml to use actions/checkout@v6 instead of v4 in both jobs. This brings the workflow up to the newer checkout action version to pick up improvements and fixes.

20260611

PBS-style date-keyed releases + Node 24 actions (#14)

• Date-keyed releases (PBS-style): full version in filenames

Restructures the publish step so that a manually triggered workflow_dispatch
with a release_date input (YYYYMMDD) produces a single GitHub release
tagged by that date, containing every per-platform tarball from every
matrix entry. Mirrors what astral-sh/python-build-standalone already does
and what we already consume in flet-dev/serious-python's package_command
via _release.standaloneReleaseDate.

Why move away from one-release-per-python-minor:

• Re-cutting a release for a build fix (e.g. the Python.app strip we
  just landed) currently has to clobber an existing tag, which breaks
  reproducibility for any downstream that pinned to it.
• Several platform fixes in the past month had to wait for a coordinated
  "all minor versions get a fresh tarball" moment; date tags decouple
  that — we just cut a new date once everything we care about builds.
• Symmetric with how flet-dev/serious-python's package_command resolves
  its astral-sh CPython tarball: pin a date, not a minor.

v3.14

Merge pull request #1 from flet-dev/android

Android support

v3.13

Merge pull request #1 from flet-dev/android

Android support

v3.12

Build Python for Android