6 Commits

Include renames

Author	SHA1	Message	Date
stroblme	8a645da974	Release v0.1.2	2026-08-25 12:54:41 +02:00
stroblme	91953185ef	Release v0.1.1	2026-08-24 21:33:18 +02:00
stroblme	449214c0e5	Fix the CI gates: Python 3.13, concurrency groups, hook violations ... 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.	2026-08-24 14:55:59 +02:00
stroblme	a5a8127550	License the workspace under AGPL-3.0-or-later ... Replace the empty LICENSE placeholders with the verbatim GNU AGPL v3 text, fix the invalid "AGPLv3" SPDX string in the package metadata, and name Melvin Strobl as the copyright holder wherever the old footers said "Fluksio ... all rights reserved".	2026-08-24 11:53:54 +02:00
stroblme	694731de15	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.	2026-08-24 11:21:33 +02:00
stroblme	e3171f87e2	Split the worker into a distribution of its own ... A cluster or GPU host installs `pip install fluksio-worker` and gets the agent and the runner, not psycopg, numpy and the MCP SDK. The engine depends on it as a workspace member, so the file it launches node code with is the same file a remote worker runs — which is what keeps a node unable to tell the difference. Copying the two files by hand still works.	2026-08-21 21:54:10 +02:00