Fluksio/app - app

4 Commits

Include renames

Author	SHA1	Message	Date
stroblme	e2b25c9d5a	wording Docs / docs (push) Successful in 49s Details Playwright Tests / test-playwright (1, 2) (push) Failing after 29s Details Playwright Tests / test-playwright (2, 2) (push) Failing after 22s Details pre-commit / pre-commit (push) Successful in 3m3s Details Test Backend / test-backend (push) Successful in 2m19s Details Compose Smoke Test / test-compose (push) Failing after 24s Details Playwright Tests / merge-reports (push) Failing after 1m5s Details Signed-off-by: stroblme <stroblme@posteo.de>	2026-08-24 15:12:00 +02:00
stroblmeandClaude Opus 5	d4a9406c51	Fix the CI gates: Python 3.13, concurrency groups, hook violations Docs / docs (push) Successful in 49s Details Playwright Tests / test-playwright (1, 2) (push) Failing after 1m11s Details Playwright Tests / test-playwright (2, 2) (push) Failing after 23s Details pre-commit / pre-commit (push) Successful in 3m2s Details Test Backend / test-backend (push) Successful in 2m22s Details Compose Smoke Test / test-compose (push) Failing after 22s Details Playwright Tests / merge-reports (push) Canceled after 1s Details The gates have never gone green on the new runners. Three separate reasons: - backend/Dockerfile shipped Python 3.10 while the code imports typing.Self and datetime.UTC, so the container exited on import and the suite could not even load its conftest. The image moves to 3.13 and the packages declare >=3.12, which is the floor the tests actually pass on; ruff's target follows and rewrites timezone.utc and asyncio.TimeoutError accordingly. Relocking drops the 3.10 branch, which bumps FastAPI and so regenerates the SDK. - frontend/README.md had no trailing newline and two dashboard widgets used arbitrary text-[…] sizes. Both are em-relative on purpose, so they move to the inline style the neighbouring ramp already uses. - Every commit left its own run queued: without a concurrency group a runner that was offline for a while works through a backlog nobody reads. A stack that fails to come up now prints its logs before the teardown removes it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-24 14:55:59 +02:00
stroblmeandClaude Fable 5	36575c5855	Say the licence on the two pages PyPI will show Publish / publish (push) Successful in 55s Details Docs / docs (push) Successful in 53s Details Playwright Tests / test-playwright (1, 2) (push) Failing after 39s Details Playwright Tests / test-playwright (2, 2) (push) Failing after 13s Details pre-commit / pre-commit (push) Failing after 2m24s Details Test Backend / test-backend (push) Failing after 49s Details Compose Smoke Test / test-compose (push) Failing after 14s Details Playwright Tests / merge-reports (push) Failing after 22s Details Every other README carries the AGPL line; these two did not, and they are the ones that become pypi.org/project/fluksio and /fluksio-worker — the most public surface the project has, and the place a copyleft licence is least useful to have to go looking for. §13 is named outright for the same reason. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012ue1tkFWB1bcGy3aWhCKpU	2026-08-24 12:51:53 +02:00
stroblmeandClaude Fable 5	11e60cb6a8	Make both distributions fit to publish The release workflow was already right; what it would have uploaded was not. `fluksio` had no readme, so its PyPI page would have been blank — the app repo's own README is a contributor's map of `frontend/` and `docker/`, which is the wrong front page for `pip install fluksio`. It now has one of its own, aimed at somebody who landed on the project page. Both distributions gain authors, urls, keywords and classifiers; `twine check` passes clean on all four artifacts where it warned on two before. The workflow publishes `fluksio-worker` first, because `fluksio` depends on it and the other order leaves a few seconds — the whole of a first release — in which the dependency cannot be resolved. `--check-url` makes a re-run skip what is already uploaded rather than failing on it, which matters because a version on PyPI can never be replaced. Licence metadata is deliberately still absent: LICENSE is MIT in somebody else's name, inherited from the template this was scaffolded from, and whose it should be is not a decision to make in a commit. NOTEPAD carries it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012ue1tkFWB1bcGy3aWhCKpU	2026-08-24 11:21:33 +02:00