chore: merge origin/main

This commit is contained in:
Abdessamad Derraz committed 2026-11-09 14:02:45 +01:00
commit 025fd08a72
16 files changed
+484 -9

No files matched your search

+17 -2
View File
@@ -110,8 +110,8 @@ scripts stay Python.
`platforms/**`, `emulators/**`, `schemas/**`, `scripts/**`, `tests/**`,
`install.py`, `install.sh` or `install.ps1` (the bootstraps pin the
installer's SHA-256, so editing one without the other fails the run),
`ports/**` (the handheld port bundles the installer), or any input of the site
build. The path lists are spelled out once per event because the workflow
`ports/**` (the handheld port bundles the installer), `packaging/**` (the PyPI
package is built from it), or any input of the site build. The path lists are spelled out once per event because the workflow
parser reads no YAML anchor, and a test holds the two equal.
**Concurrency.** Per-PR group on a pull request, per-ref on a push. A pull
@@ -312,6 +312,21 @@ git status --short
git add release.json README.md install/*.json install/targets/*.json
git commit -m "chore: record release v${DATE}" && git push
# 5b. The PyPI package, `uvx retrobios`: install.py and its command. The
# version is the UTC date of the last commit that changed install.py
# (2026-11-09 gives 2026.11.9, the third change that day 2026.11.9.3),
# so an unchanged install.py keeps its version and PyPI refuses it
# again. Publishing is not tied to a release: any push that changes
# install.py can be published. The build replaces any earlier one in
# tmp/pypi-dist. `uv build` builds it with the flit_core backend the
# project pins, dated by that commit (SOURCE_DATE_EPOCH), so a rebuild
# gives the same bytes. Build, run the wheel, then upload the two files. The
# token stays in its file: never in the repository, a script or a log.
python scripts/build_pypi.py --output-dir tmp/pypi-dist
python -m unittest tests.test_pypi_package
uvx --from tmp/pypi-dist/retrobios-*.whl retrobios --help
uv publish --token "$(cat ~/.config/retrobios/pypi-token)" tmp/pypi-dist/*
# 6. Keep only the new release plus large-files: an older pack carries hashes
# the platforms no longer check, so it misleads more than it helps
gh release list --json tagName,createdAt \