Converges the sprinkle of -tags=gms_pure_go fixes into a single source plus a source-time CI guard. .buildflags is now canonical (exports GOFLAGS, CGO_ENABLED), scripts source it, scripts/check-build-tags.sh runs in CI to catch bare go commands. Fixes 5 latent bugs the guard caught (regression.yml, Makefile bench/test-regression, devcontainer, embedded-test-shard fallback, smoke-test scripts).
Remove push-to-main and PR triggers from cross-version smoke test
workflow — 30-45 min runtime is too costly for every push. Keep tag
pushes (releases/RCs) and manual dispatch.
Add a visible warning when >80% of tested versions are skipped, printed
to stderr and GitHub step summary. Prevents silent "all passed" when
nearly nothing actually ran.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Pre-embeddeddolt versions only populate issues.jsonl via git hooks on
commit. Without committing, the JSONL stays empty and recovery is
impossible.
- Add git commit after creating test data with the old binary
- Use bd init --from-jsonl when candidate suggests bd init and JSONL
has data, enabling recovery from SQLite/server-mode eras
- Fix bash 3.x compatibility (${array[-1]} not supported on macOS)
This turns v0.50.x from FAIL to PASS (recovered via init --from-jsonl).
The dolt-server-era binaries (v0.57-v0.62) start background processes
that cause set -e to trigger on non-zero exits deep in subshells.
set -uo pipefail is sufficient for error detection.
Also kill auto-started candidate dolt servers after verify, and use
pkill by workspace path for thorough cleanup.
When direct read fails and the candidate tells the user to
"run bd init", follow that advice and retest. This is fair play
since the user would see and follow the hint.
Catches additional bugs:
- dash in prefix breaks embedded Dolt database naming
- auto-import from issues.jsonl doesn't fire after bd init
The candidate says "no beads database found" without mentioning
init --from-jsonl or any migration path. Testing a path that no
user would discover makes the test dishonest.
When direct read fails but old version exported issues.jsonl,
retry with candidate's init --from-jsonl. Reports "passed (after
migration)" to distinguish from direct compatibility.
Also use prefix with underscore and dash (sm-o_ke) to catch
special character issues in issue IDs.
Instead of raw kill, use the old binary's own stop commands
(bd daemon stop, bd dolt stop) for clean shutdown. Falls back
to pid files only if the commands fail.
- run old binaries from workspace cwd (not --db flag, breaks old versions)
- install dolt in CI for server-mode versions (v0.56-v0.62)
- fix pipefail handling that silently killed the script mid-run
- add results table output and GitHub Actions step summary
- report real failures instead of silently skipping broken upgrades
Tests that data created with old bd versions (epic, issues, dependencies)
is readable after upgrading to the candidate binary. Covers the last 30
release tags by default, with --from flag for broader sweeps.