Release: v1.0.0-beta-8 — what bb setup switches on, it now ships

A bugfix release. Six fixes, and four of them are on the bb setup path — the step between a generated project and the first (go).

1.0.0-beta-7 let you pick Replicate in the setup wizard. Picking it produced a project that could not boot, because the wizard enabled a component whose library was not on the classpath. The same hole covered PostgreSQL and MySQL. That is the headline fix; the rest are what we found next to it.

Fixed: bb setup wrote a project that could not boot

bb setup --ai-provider <name> enabled :wagoe/ai-service in config.edn while wagoe-ai was declared only in the :mcp alias, so (go) threw. --database postgresql and --database mysql had the same shape (BOU-414). Those libraries now ship in the generated deps.edn, and the release matrix has cells that boot with an AI provider enabled, so the next regression fails a build rather than a first run.

Fixed: bb setup tells you what the provider needs

The config a provider needs is written by bb setup. What it needs outside the config was nowhere: the project booted, and the first AI call failed (BOU-415). Setup now closes with it — install and pull for Ollama, the key URL and the export for Anthropic, OpenAI and Replicate. The AI library page has the same table.

One line in it is worth repeating here, because we suggested .env files without saying so: .env does not load itself. Plain source .env sets shell variables without exporting them, and the JVM never sees them. Use

set -a; source .env; set +a

bb doctor --ci names a missing key for the hosted providers. It does not probe whether Ollama is running.

Fixed: bb setup dropped the dev error enricher

wagoe new configures :wagoe/dev-error-enricher in the dev profile; bb setup rewrote the config without it (BOU-416). If setup rewrote your config before this release, add :wagoe/dev-error-enricher {} under the dev :active map to get it back.

Fixed: bb repl gave you no prompt

bb repl started an nREPL server and returned to the shell, so there was nothing to type (go) into (BOU-403). It now starts the prompt and the server. clojure -M:repl stays headless for editors that connect on the port.

Fixed: two versions the docs got wrong

The stability page named the previous release as current (BOU-413). Its current-version cell is exempt from the version check for a reason — the page explains why 1.0.0-beta-1 sorts older than 1.0.1-alpha-42, and a bump would have rewritten that explanation — but the exemption covered the whole file, and the one cell that should move did not. The exemption is now per rule, and that cell is gated.

The manual bbin install command pinned --tag v1.0.0-beta-N (BOU-412). Our tags carry no v prefix, so the documented command resolved no ref, and the version gate required the prefix, so it verified the broken spelling every release. The corrected command:

bbin install https://github.com/wagoebv/wagoe \
  --tag 1.0.0-beta-8 \
  --git/root libs/wagoe-cli \
  --main-opts '["-m" "wagoe.cli.main"]'

Version alignment

All 31 artifacts bumped to v1.0.0-beta-8 to maintain lockstep versioning.

Upgrade

Re-run the installer to pick up the latest release:

curl -fsSL https://get.wagoe.org | bash

No breaking changes. Two things to check in an existing project: if you ran bb setup --ai-provider or --database on beta-7, add the matching library to deps.edn or run setup again on this release; and if setup rewrote your config, put :wagoe/dev-error-enricher {} back under dev :active.