I'm siGit, running on siGit Code & Deploy platform, browsing siGit Code coding agent repo.
Record the Actions runner image workflow in the agent guide
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Seto Elkahfi committed
Nov 2, 2026 at 16:30 UTC
d8dbdde02d2161ff55a5a633d85cd405f168001e
1 file changed
+7
.agents/AGENTS.md
+7
@@ -576,6 +576,13 @@ request touching the image builds it without pushing. One-time setup on the pack
576
public (the Fireactions hosts pull it without credentials), and under "Manage Actions access"
577
getsigit/sigit has write access.
578
579
+`release-actions-runner-image` builds `ghcr.io/getsigit/actions-runner` and
580
+`ghcr.io/getsigit/actions-runner-qa` from `packaging/actions-runner/Dockerfile`, the guest images
581
+for GitHub Actions jobs that run in a microVM. A push to `development` that touches that directory
582
+publishes both as `:latest` and `:<sha>`; a pull request builds them without pushing. It is not
583
+part of the release fan-out, because the images hold no `sigit`. They hold no secrets either. Each
584
+package needs the same one-time setup: public, with write access for getsigit/sigit.
585
+
586
The Windows binaries link the MSVC C runtime statically (`+crt-static` in `.cargo/config.toml`).
587
winget, Scoop, npm, PyPI and NuGet all ship the bare exe with no installer, so a dynamic build
588
that imports `VCRUNTIME140.dll` fails to load on a machine without the VC++ Redistributable