A small release, and every item in it is about the gap between what we test and what you get.
1.0.0-beta-6 fixed bb scaffold ai and shipped it pointing at the previous release. The version checker covered 96 locations and none of them were the pins the scaffolder writes into your project. The nightly smoke ran against main, so a release could be broken for weeks without a single red build. That set of holes is what this release closes.
Fixed: bb scaffold ran a release-old CLI in your project
bb scaffold and bb scaffold ai injected scaffolder-version and ai-version a release behind (BOU-406). A beta-6 project scaffolded with the beta-5 scaffolder — bb quickstart reported success, and (go) then died on No wiring for module :wagoe/tasks. bb scaffold ai reached the beta-5 AI CLI, which has no scaffold-parse subcommand, and stopped on Unknown subcommand: scaffold-parse.
Those two pins were ungated: nothing checked them, so the release process could not have caught it. bb check:versions now gates injected pins (BOU-317). The AI scaffolding step works in a published release for the first time.
Fixed: install.sh blamed your connection for GitHub’s rate limit
The installer resolves the latest release through the GitHub API. Unauthenticated, that is 60 requests an hour per IP — reachable on a shared or CI address without doing anything unusual. Every failure came out as a message about checking your internet connection, which sends you to debug the wrong thing (BOU-410).
It now reads the rate-limit headers, says how long until the limit clears, and honours GITHUB_TOKEN for 5000 requests an hour:
GITHUB_TOKEN=ghp_… curl -fsSL https://get.wagoe.org | bashFixed: bb setup could not configure Replicate
Replicate was a supported AI provider that the setup wizard would not let you pick (BOU-411). Choose it in the wizard, pass --ai-provider replicate, or ask for it in bb setup ai. An unrecognised provider name is now refused with the valid choices rather than accepted and left to fail later.
Added: the nightly smoke runs the published tag
SMOKE_TARGET=released runs the first-run smoke against the release as a visitor gets it — installer, published artifacts, real tag (BOU-402). It runs nightly.
The smoke already existed; it ran against main, where the fix always landed first. That is how beta-5 shipped a broken (status) and kept it for weeks. A green build on the branch says nothing about what is installable, and now something checks the difference. The same change prints the gate output the smoke had been discarding, so a failure says what failed.
bb check:versions also reads the version claim in prose, not just in code (BOU-317). 96 gated locations become 105.
Version alignment
All 31 artifacts bumped to v1.0.0-beta-7 to maintain lockstep versioning.
Upgrade
Re-run the installer to pick up the latest release:
curl -fsSL https://get.wagoe.org | bashNo breaking changes and no migration. If you generated a project with beta-6 and hit No wiring for module :wagoe/tasks, the pins in its deps.edn are the cause — point them at 1.0.0-beta-7 and it will boot, or scaffold again on this release.