You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use installed Alloy binary instead of docker in CI check
The Alloy team documents `alloy fmt --test` and `alloy validate` as the
CI contract (exit codes signal pass/fail) but ships no dedicated
setup/fmt/validate GitHub Action, so we invoke the CLI ourselves. Running
it through `docker run` required overriding the image entrypoint and a
mounted-volume find loop; installing the released binary is simpler and
faster.
Download the alloy-linux-amd64 release matching the version pinned in the
Dockerfile (keeping CI in parity with production), then run `alloy fmt -t`
per file and `alloy validate` over the config directory. The format loop
uses `find` rather than a bash globstar so it can never silently match
zero files.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments