4 Commits

Include renames

Author	SHA1	Message	Date
Admin Bot	eaeeb97b2a	feat: k8s informer for ServiceAdapter CRDs, bump CI to go1.26 ... - Add dynamic-client informer to watch ServiceAdapter CRs in-cluster - Remove typed scheme registration (dynamic client needs no DeepCopy) - Bump Dockerfile + CI images from golang:1.25 to golang:1.26 (k8s.io/[email protected] requires go>=1.26) - Wire informer into main.go startup with graceful fallback	2026-08-26 14:38:12 -07:00
Story Crater Bot	0aaf4116f1	fix(ci): target the golang runner, generic docker runner retired	2026-08-21 16:53:05 -07:00
Story Crater Bot	7ebbf2bd03	fix: install node in job containers so actions/checkout can exec ... actions/checkout@v4 is a JS action; Forgejo Actions runs it via node, which neither golang:1.25-bookworm nor docker:27-cli ship. Every run since the .gitea/workflows move has failed identically: 'exec: node: executable file not found in $PATH' during the checkout step, before any real job step ran. Verified locally against both exact images before pushing: - golang:1.25-bookworm: apt-get install nodejs ca-certificates git -> node v18.20.4, git 2.39.5. - docker:27-cli: apk add nodejs git -> node v22.23.2, git 2.47.2, and actions/checkout's dist/index.js actually executes afterward (confirmed by invoking it directly) instead of failing on a missing binary. - The Dockerfile itself builds clean end to end and the resulting image serves /healthz, so checkout was the only remaining blocker in the path.	2026-08-21 13:49:24 -07:00
Story Crater Bot	dac1a5da4b	fix: move workflows from .forgejo/workflows to .gitea/workflows ... .forgejo/workflows/*.yaml never creates an action_run on push on this Forgejo instance (1.27.0) -- confirmed directly in the action_run table across multiple probe pushes. .gitea/workflows fires immediately with an identical spec. This is why build.yaml never once executed.	2026-08-21 11:36:34 -07:00