v3.2.0 - Channels, runtime drift warning, CI smoke test (Phase 6b)
Phase 6b — Channels, runtime drift warning, CI smoke test. Backward compatible with v3.0 and v3.1.
Highlights
BMAD release channels
New -Channel / --channel flag on install.* and update.*:
stable(default) — pinned BMAD6.2.2, the only fully tested combinationbeta— latest npmnextdist-tag (UNSUPPORTED)nightly— alias forbeta
When you select a non-stable channel, the installer prints a yellow warning box with the resolved version and requires interactive confirmation. Verified live: -Channel beta resolved to 6.2.3-next.30 from npm.
.\scripts\install.ps1 -Channel beta./scripts/install.sh --channel betaRuntime drift warning
Added a non-fatal compatibility check to bmad-agent-team-guide activation. On every invocation, the agent reads compatibility.json, detects the installed BMAD version, and warns the user if it's blocked, untested-in-range, or out-of-range. Never blocks the user from proceeding.
GitHub Actions CI smoke test
New .github/workflows/smoke-test.yml runs the full install + compat-check + doctor + bmad status pipeline across {ubuntu-latest, windows-latest} × {Node 18, 20, 22} on every push, pull_request, daily cron at 04:17 UTC, and manual dispatch. Aggregate summary job reports a single pass/fail at the end.
This catches BMAD upstream regressions automatically — if a future BMAD release breaks TeamBuilder, the daily cron run will fail and surface the issue immediately.
Updating from v3.0 or v3.1
# Windows
.\scripts\update.ps1# Linux/macOS
bash scripts/update.shupdate.* detects any v3.x install, snapshots it, and upgrades in place to v3.2 with no manual steps.
Validation
All 6 Phase 6b tests pass: default install (stable, no warning), version bump verification, doctor on new install (44 PASS), beta channel live-resolves from npm with warning displayed, invalid channel rejected by ValidateSet, smoke-test.yml structure valid.
See CHANGELOG.md for the complete per-section diff.
Phase 6 retrospective
Phase 6 (a + b) is now complete. TeamBuilder v3.2.0 has full guardrails:
- ✅ Pinned BMAD version (no
@latestdrift) - ✅ Structural invariants in
compatibility.json - ✅ Read-only diagnostics (
doctor.*) - ✅ Safe in-place updates with rollback (
update.*) - ✅ Opt-in beta/nightly channels (
-Channel beta/--channel nightly) - ✅ Runtime drift warnings at agent activation
- ✅ Cross-platform CI smoke test on every push and daily cron