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.