8 Commits

Include renames

Author	SHA1	Message	Date
lars	0f7febfd02	ci: set UV_LINK_MODE=copy to silence the cross-filesystem hardlink warning ... The bind-mounted uv cache and the job workspace are on different filesystems, so uv already falls back to copying installed files; this just tells it to do so directly instead of logging a hardlink-failed warning every job.	2026-07-27 14:40:01 +02:00
lars	19be455346	ci: re-pin UV_CACHE_DIR after setup-uv, which exports its own value regardless of enable-cache ... Log evidence showed setup-uv still sets UV_CACHE_DIR to a tool-cache tmp path (/tmp/setup-uv-cache) even with enable-cache: false, clobbering the workflow env pointing at the bind-mounted cache. Re-export it via GITHUB_ENV in a step right after setup-uv so it wins for the rest of the job.	2026-07-27 14:31:22 +02:00
lars	1787d26d1c	ci: stop setup-uv from overriding UV_CACHE_DIR ... setup-uv's default enable-cache: auto sets its own UV_CACHE_DIR (a tool-cache tmp path) as a later step, clobbering the workflow-level UV_CACHE_DIR that points at the bind-mounted persistent cache. Disable setup-uv's own cache handling so our mount stays in effect.	2026-07-27 14:22:49 +02:00
lars	0afa75ee30	ci: replace unsupported artifact sharing with a bind-mounted uv cache ... The self-hosted act_runner doesn't support upload/download-artifact, so drop that plumbing and instead run jobs in an explicit container with a persistent host directory mounted at /uv-cache (UV_CACHE_DIR), backed by valid_volumes on the runner. uv sync still runs per job but hits a warm local cache instead of re-downloading/building packages every time.	2026-07-27 14:18:54 +02:00
lars	08c76a9614	ci: share one uv sync across jobs, gate tests on lint+type-check, sync tag/version on release tags ... Uploads the synced .venv as an artifact from a single setup job instead of re-running uv sync (and re-downloading torch) in every job. Drops the build/publish job in favor of a lighter job that, on a pushed tag, checks the tag against the uv project version and — if they differ — bumps the version, commits it to master, and recreates the tag on the new commit.	2026-07-27 14:00:59 +02:00
larsandClaude Sonnet 5	9162ba7ae0	Split CI lint stage into parallel jobs ... ruff check, ruff format check, ty check, and pytest now run as four independent jobs instead of one sequential lint job gating test — faster wall-clock CI since none of these checks depend on each other. build still waits on all four before bumping/publishing. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-23 14:38:46 +02:00
larsandClaude Sonnet 5	faac19edf3	Quote the on: key in the CI workflow ... Unquoted on: gets parsed as the YAML 1.1 boolean true instead of the string "on", so Gitea couldn't find a trigger key and didn't register the workflow at all. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-23 14:35:55 +02:00
larsandClaude Sonnet 5	4e77e3fc4b	Add Gitea Actions CI pipeline ... Three-stage workflow: lint/format/type-check (ruff, ty), pytest, and (master pushes only) a version-bump + uv build + publish to the Gitea package registry. Bump commit is tagged [skip ci] to avoid retriggering the workflow. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-23 14:33:15 +02:00