Repository navigation
v1.1.5 — fix: codeforge user back at UID 1000
Fixes v1.1.4, do not run v1.1.4 on an existing data volume.
- v1.1.4 moved the runtime to
node:22-alpine, whose built-innodeuser takes UID 1000, socodeforgebecame UID 1001 and could not write a/datavolume created by v1.1.3 or older (opening sqlite: attempt to write a readonly database, crash loop). Thecodeforgeuser is UID/GID 1000 again, in both thecodeforgeandcodeforge-actionimages.
Everything from v1.1.4 is included: Node.js 22.23.4 runtime (Node.js security release of 2026-10-21), tenant isolation and GitLab command authorization (#49), OpenTelemetry 1.45.0 (#47).