• v1.2.1 1016fa6374

    v1.2.1
    All checks were successful
    CI / build-and-test (push) Successful in 1m55s
    CI / docker-build (push) Successful in 20s
    Stable

    joeyrendar released this 2026-07-12 20:45:06 -05:00 | 39 commits to main since this release

    CI and test hygiene that restores a fully green pipeline. No change to the bot's runtime, built image, or command surface.

    Fixed

    • build-and-test CI is green again. The config-validation tests built their "valid base config" without BRAVE_SEARCH_API_KEY, then depended on it being present in the ambient environment — config.ts loads dotenv over ['.env', '.env.config'], and the committed .env.config sets ENABLE_ADMIN_TOOLS=true, so validate() requires the key for web_search. It was present locally (from .env) but absent in CI, so two "should validate successfully" cases threw only there. The base config now pins the key and is self-contained. Separately, files that were not Prettier-clean (CHANGELOG.md, four __tests__ files, WHATS_LEFT.md) were formatted so format:check — the job's first step — stops aborting the run.
    • docker-build CI is green. The Forgejo Actions runner now mounts the host Docker socket into job containers, so the image build reaches the daemon (previously it failed with "cannot connect to the Docker daemon"). This needs both container.options (with -v /var/run/docker.sock:/var/run/docker.sock) and container.valid_volumes: [/var/run/docker.sock] — the runner validates -v mounts against valid_volumes, which defaults to deny-all. Set in the forgejo-runner.yaml Swarm stack; the ci.yml comment is corrected to match.

    Changed

    • WHATS_LEFT.md: removed the closed SECURITY.md (A3) item and dropped P5-1 (CI docker-build) now that it is done.
    Downloads