siftlode

1,656 Commits 1 Branch 72 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
peter	434a98d6ed	chore(lint): set ruff line-length 100 and gate ruff format --check Adds ruff's formatter to the gate. line-length 100 matches the frontend prettier printWidth. The reformat itself lands as the next commit (kept separate so it can go in .git-blame-ignore-revs).	2026-08-23 07:42:42 +02:00
peter	44d4e4876d	build(deps): pin a reproducible lock + pip-audit; bump node 20->22 (E1 S4, SEC-5/DX-3) requirements.txt stays the source (floor ranges); requirements.lock pins the exact resolved versions (generated in the python:3.12-slim prod base, extras like psycopg-binary/uvloop included). The prod Dockerfile, Dockerfile.test and CI now install the lock, so the image is reproducible and the versions are the ones pip-audit scans. CI gains a non-blocking pip-audit step over the lock. The frontend build + CI move from the EOL node 20 to node 22.	2026-08-18 02:34:45 +02:00
peter	54ba92bb05	ci(gitea): add the server-side gate mirror (E1 S3, DX-1) gate / backend (push) Successful in 1m13s gate / frontend (push) Successful in 51s Add .gitea/workflows/check.yml so the quality gate runs on the lab act_runner, machine-independent, on every push/PR — the review's "no server-side CI" gap. Two parallel jobs mirror the two local lanes: - frontend (node:20-bookworm, matching the prod build image): tsc + eslint + prettier --check + knip + vitest. - backend (nikolaik/python-nodejs python3.12+node): ruff + the full pytest suite against a real postgres:16 service, with ffmpeg installed and SIFTLODE_TEST_REQUIRE_DB=1 so a DB/ffmpeg that failed to come up is a hard error, never a silent skip. Notes for this runner: pytest runs natively against the service (the docker-compose bind-mount is unreliable under a mounted-socket runner), and the backend uses a baked python+node image rather than actions/setup-python, which can't reach GitHub's python-versions download from the lab.	2026-08-18 01:59:36 +02:00

Author

SHA1

Message

Date

peter

434a98d6ed

chore(lint): set ruff line-length 100 and gate ruff format --check

Adds ruff's formatter to the gate. line-length 100 matches the frontend
prettier printWidth. The reformat itself lands as the next commit (kept
separate so it can go in .git-blame-ignore-revs).

2026-08-23 07:42:42 +02:00

peter

44d4e4876d

build(deps): pin a reproducible lock + pip-audit; bump node 20->22 (E1 S4, SEC-5/DX-3)

requirements.txt stays the source (floor ranges); requirements.lock pins the
exact resolved versions (generated in the python:3.12-slim prod base, extras like
psycopg-binary/uvloop included). The prod Dockerfile, Dockerfile.test and CI now
install the lock, so the image is reproducible and the versions are the ones
pip-audit scans. CI gains a non-blocking pip-audit step over the lock. The
frontend build + CI move from the EOL node 20 to node 22.

2026-08-18 02:34:45 +02:00

peter

54ba92bb05

ci(gitea): add the server-side gate mirror (E1 S3, DX-1)

gate / backend (push) Successful in 1m13s

gate / frontend (push) Successful in 51s

Add .gitea/workflows/check.yml so the quality gate runs on the lab act_runner,
machine-independent, on every push/PR — the review's "no server-side CI" gap.
Two parallel jobs mirror the two local lanes:
- frontend (node:20-bookworm, matching the prod build image): tsc + eslint +
  prettier --check + knip + vitest.
- backend (nikolaik/python-nodejs python3.12+node): ruff + the full pytest suite
  against a real postgres:16 service, with ffmpeg installed and
  SIFTLODE_TEST_REQUIRE_DB=1 so a DB/ffmpeg that failed to come up is a hard
  error, never a silent skip.

Notes for this runner: pytest runs natively against the service (the
docker-compose bind-mount is unreliable under a mounted-socket runner), and the
backend uses a baked python+node image rather than actions/setup-python, which
can't reach GitHub's python-versions download from the lab.

2026-08-18 01:59:36 +02:00