-
v1.2.1
Stablereleased this
2026-07-12 20:45:06 -05:00 | 39 commits to main since this releaseCI and test hygiene that restores a fully green pipeline. No change to the bot's runtime, built image, or command surface.
Fixed
build-and-testCI is green again. The config-validation tests built their "valid base config" withoutBRAVE_SEARCH_API_KEY, then depended on it being present in the ambient environment —config.tsloads dotenv over['.env', '.env.config'], and the committed.env.configsetsENABLE_ADMIN_TOOLS=true, sovalidate()requires the key forweb_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 soformat:check— the job's first step — stops aborting the run.docker-buildCI 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 bothcontainer.options(with-v /var/run/docker.sock:/var/run/docker.sock) andcontainer.valid_volumes: [/var/run/docker.sock]— the runner validates-vmounts againstvalid_volumes, which defaults to deny-all. Set in theforgejo-runner.yamlSwarm stack; theci.ymlcomment is corrected to match.
Changed
WHATS_LEFT.md: removed the closed SECURITY.md (A3) item and dropped P5-1 (CIdocker-build) now that it is done.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads