3 Commits

Include renames

Author	SHA1	Message	Date
levaliciousandClaude Opus 5.5	4cf88d674c	ci: check out the tools submodule ... reweave/build's `make all` also builds tools/runner from the tools submodule (weaveworks/build-tools); run 7 compiled every weave binary and then stopped there. Fetched from upstream for now, like the build's other fetches. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UHXzGrsxfkGk8LmwrBbHNZ	2026-10-12 17:42:52 -04:00
levaliciousandClaude Opus 5.5	8d36dc2f9b	ci: push images as the reweave-ci bot ... Gitea's registry refuses the job token (no package scope at login), so log in as reweave-ci with the org secret REGISTRY_TOKEN, and drop the packages permission that had no effect. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UHXzGrsxfkGk8LmwrBbHNZ	2026-10-12 17:18:15 -04:00
levaliciousandClaude Opus 5.5	6260533b6d	ci: build weave-kube and weave-npc, push to this Gitea's registry ... A Gitea Actions workflow that builds the two images the cluster runs from reweave/build/Dockerfile (linux/amd64 only) and pushes them to git.levk.dev/reweave/{weave-kube,weave-npc}, tagged with the full commit SHA so a tag never changes meaning. It stops at the push; rollout is the CD side's job. Build-time fetches (base images, apt/apk, Go modules) stay external for now and are to be peeled out once self-deploy works. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UHXzGrsxfkGk8LmwrBbHNZ	2026-10-12 17:12:04 -04:00