* fix(dolt): retry mutate+commit methods on serialization conflict (1213/1205) ClaimIssue, ClaimReadyIssue, UpdateIssue and CloseIssue each hand-rolled their own tx (BeginTx + DOLT_ADD/DOLT_COMMIT + Commit) outside withRetryTx, so a concurrent writer that lost Dolt's optimistic commit-time merge surfaced MySQL 1213/1205 as a hard failure instead of retrying. Dolt has no real row locking — FOR UPDATE / SKIP LOCKED are parse-only no-ops (https://www.dolthub.com/blog/2023-10-23-hold-my-beer/) — so retry is the only safety net under N concurrent workers. These four are the work-queue hot paths: `bd ready --claim`, claim, update, close. Move each body into a withRetryTx closure (which owns BeginTx and the final Commit and retries serialization failures with backoff), preserving the single-tx CAS/mutation + DOLT_COMMIT atomicity exactly. On retry, ClaimReadyIssue re-scans the ready front from a fresh snapshot and claims the next available issue. Tested: TestEmbeddedReadyClaimConcurrent, TestEmbeddedReadyConcurrent, TestEmbeddedCloseConcurrent, TestEmbeddedUpdateConcurrent and the non-concurrent embedded Update/Close/Ready tests pass; build + vet clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * test(dolt): add concurrent work-queue drain test (Gas Station claim invariant) N workers concurrently dequeue one shared ready-front via ClaimReadyIssue until empty; asserts every issue claimed exactly once, none stranded, no double-claims, and no serialization error ever surfaces (withRetryTx absorbs the 1213/1205 from the claim-CAS cell collision). This is the regression guard for the multi-agent claim queue that #4491 makes safe. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(lease): claim-TTL + heartbeat + reclaim for dead-worker recovery Gas Station v1.1 (wy-5r9j). A claim was previously permanent: a worker that died mid-task stranded its issue in_progress forever. This adds a lease so a claim can expire and be recovered. Schema (migration 0054): add lease_expires_at, heartbeat_at (DATETIME) and row_lock (BIGINT) to issues (and wisps, for uniform issueops routing), plus idx_issues_lease for the reaper scan. assignee doubles as the lease owner. Lifecycle (shared issueops, so both server-mode DoltStore and EmbeddedDoltStore get it): - Claim stamps lease_expires_at = now + TTL (default 5m, WithLeaseTTL to override), heartbeat_at = now, and a fresh row_lock. - bd heartbeat <id> — owner-only; pushes the lease forward and rewrites row_lock. Fails (ErrNotClaimable/ErrAlreadyClaimed) once the lease is gone. - bd reclaim --older-than <dur> — reverts in_progress issues whose lease expired more than <dur> ago back to ready (clears assignee/started_at, records a lease_reclaimed event). Default grace 2×TTL. The row_lock trick: Dolt has no row locking and merges concurrent commits cell-by-cell, so a heartbeat (writes heartbeat_at) racing a reclaim (writes status) would silently cell-merge into a zombie — an open/unassigned issue that still carries the worker's fresh heartbeat. Every mutating path (claim, close, update, heartbeat, reclaim) now rewrites the shared row_lock cell, forcing the loser to a 1213/1205 serialization conflict that withRetryTx replays. All lease paths are withRetryTx/withConn wrapped. Tests (real Dolt): TestRowLockForcesConflictOnDisjointCellWrites proves the bug without row_lock (silent merge to zombie) and correctness with it (conflict); TestConcurrentHeartbeatReclaimClose is the integration race (live workers heartbeat+close vs a continuous reaper vs dead workers) asserting exactly-once, no lost close, no zombie; plus claim/heartbeat/reclaim unit coverage on both backends. Note: lease columns are second-granular DATETIME (Dolt rounds), so sub-second TTLs are meaningless — production TTL is minutes. Heartbeat writes a Dolt commit, so cadence must stay ≪ claim cadence to avoid history bloat. Fixes the test coupling in TestMigration0053PromotesRigWisps, which assumed the rig-wisp repair was always LatestVersion(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * ci+docs: allowlist lease stress tests; scope the row_lock invariant comment - Add TestConcurrentWorkQueueDrain and TestConcurrentHeartbeatReclaimClose to the check-testing-short.sh allowlist; both are real-Dolt runtime/stress skips and were failing ci-pr-policy. - freshRowLock doc said "EVERY mutating path" rewrites row_lock, which overstates it. Scope it to status/ownership/lease-mutating paths (the set the reclaim/heartbeat races care about) and document the invariant + why orthogonal-cell writers (is_blocked, compaction, deps, rename, reopen) are intentionally exempt, so a future writer does not silently reintroduce the zombie-merge bug. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(show): surface lease_expires_at/heartbeat_at in bd show (--json + text) (wy-9cdw) Migration 0054 added lease_expires_at/heartbeat_at (and internal row_lock) to the issues/wisps tables for the claim/heartbeat/reclaim leasing feature, but bd show could not observe lease state — you had to drop to raw SQL. - types.Issue: add LeaseExpiresAt/HeartbeatAt (*time.Time, omitempty), matching the StartedAt nullable-timestamp convention. row_lock stays unexported. - sqlbuild.IssueSelectColumns: append lease_expires_at, heartbeat_at to the canonical hydration list (flows to every stack via the shared constant). - issueops.ScanIssueFrom: scan + map the two nullable columns (before the trailing extra dests, keeping positional parity across all scan sites). - bd show text view: emit a muted 'Lease: expires <rel> (heartbeat <rel> ago)' line only for in_progress issues holding an active lease; add formatTimeUntil as the forward-looking mirror of formatTimeAgo. - types_test: assert lease keys appear when set, are omitted when nil, and that row_lock is never surfaced. * fix(lease): settle v54 review blockers Address #4537 review blockers before landing v54: keep heartbeat off wisps in both backends, keep direct status/assignee updates from leaving stale leases, guard the down migration, and emit reclaim JSON as snake_case. Agent-Signature: codex-gpt-5.5-high on behalf of matt wilkie * fix(lease): cover lease fields in tests and hooks Agent-Signature: codex-gpt-5.5-high on behalf of matt wilkie --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: matt wilkie <maphew@gmail.com> |
||
|---|---|---|
| .. | ||
| bench-ready-indexes | ||
| ci | ||
| hooks | ||
| migration-test | ||
| repro-dolt-hang | ||
| repro-dolt-prod-timeouts | ||
| bump-version.sh | ||
| check-build-tags.sh | ||
| check-cli-docs-drift.sh | ||
| check-doc-flags.sh | ||
| check-doc-freshness.sh | ||
| check-docs-version.sh | ||
| check-go-install-guidance.sh | ||
| check-migration-hygiene.sh | ||
| check-testing-short.sh | ||
| check-versions.sh | ||
| clean-test-tmp.sh | ||
| cross-version-smoke-test.sh | ||
| docs.md | ||
| gen-winres.sh | ||
| generate-cli-docs.sh | ||
| generate-llms-full.sh | ||
| generate-newsletter.py | ||
| generate-newsletter_README.md | ||
| gh-body-lint | ||
| install-hooks.sh | ||
| install.sh | ||
| migrate-jsonl-to-dolt.sh | ||
| migrate-sqlite-to-current.sh | ||
| pr-preflight.sh | ||
| README.md | ||
| release.sh | ||
| release_script_test.go | ||
| sign-windows.sh | ||
| snapshot-release-docs.sh | ||
| sync-website-docs.sh | ||
| test-cgo.sh | ||
| test-git-remote.sh | ||
| test-icu-path.sh | ||
| test.sh | ||
| update-nix-vendorhash.sh | ||
| update-versions.sh | ||
| update-winget.sh | ||
| upgrade-smoke-test.sh | ||
| verify-cgo.sh | ||
Beads Scripts
Utility scripts for maintaining the beads project.
ci/
Repository-owned CI command wrappers. These scripts are the source of truth for the target CI tiers; Make targets are aliases for local discoverability.
make ci-pr-core
make ci-pr-policy
make ci-pr-lint
make ci-package-mcp
make ci-package-npm
make ci-website
Each wrapper auto-detects the repository root, sources .buildflags when it
invokes Go in the default build mode, and records per-command timing through
scripts/ci/lib/timing.sh.
Broad Go test wrappers also source scripts/ci/lib/test-env.sh, which creates a
temporary HOME/XDG/Dolt root, isolates Git global/system config, clears runtime
Beads/Dolt environment variables, and sets BEADS_TEST_SKIP=dolt before tests
run. This keeps local make test and make ci-pr-core results comparable to
the fast PR-core contract even on shared agent hosts. Set
BEADS_TEST_ENV_RUN_DOLT=1 only when intentionally running the Dolt-dependent
tests through these broad wrappers, or BEADS_TEST_ENV_DISABLE=1 when debugging
against your real local configuration.
The broad Go wrappers also cap package and test parallelism to 4 by default
(GO_TEST_PKG_PARALLEL and GO_TEST_PARALLEL). This avoids turning high-core
shared hosts into a different test topology than GitHub Actions.
make ci-pr-policy includes scripts/check-testing-short.sh, which enforces
that testing.Short() is only used for runtime, stress, or large-fixture skips.
Use build tags, environment checks, or named wrappers for integration/e2e/API
boundaries.
Package gate wrappers validate publishable/package-adjacent surfaces:
make ci-package-mcpbuilds or consumes abdbinary, puts it onPATHasbd, then runs locked MCP packageuv sync, Ruff, mypy, pytest, and build checks.make ci-package-npmbuilds or consumes the native binary expected bynpm-package/bin/bd, runs the npm package test suite, and checksnpm pack --dry-run.make ci-websiteruns website dependency install, typecheck,llms-full.txtgeneration, and Docusaurus build.
Set BEADS_TEST_BD_BINARY=/path/to/bd for MCP and npm package gates to reuse a
prebuilt candidate binary instead of rebuilding it inside the wrapper.
pr-preflight.sh
Read-only PR safety check for agents and maintainers.
# Before implementing or opening a related PR
./scripts/pr-preflight.sh --search "topic keywords" --repo gastownhall/beads
# Before changing, closing, or merging an existing PR
./scripts/pr-preflight.sh 123 --repo gastownhall/beads
It reports contributor/fork status, draft/review/merge/check state, risky diff
signals such as .beads/ changes or missing tests, and the required
contributor-protection next steps. It does not replace code review or local
validation.
gh-body-lint
Lint Markdown files before posting them with gh ... --body-file.
./scripts/gh-body-lint body.md
./scripts/gh-body-lint --fix body.md
The lint catches literal \n sequences, which render poorly on GitHub, and
GH#123 references, which do not auto-link like #123 or owner/repo#123.
release.sh (⭐ The Easy Button)
One-command release from version bump to local installation.
Usage
# Full release (does everything)
./scripts/release.sh 0.9.3
# Preview what would happen
./scripts/release.sh 0.9.3 --dry-run
What It Does
This master script automates the entire release process:
- ✅ Stops running Dolt servers (avoids version conflicts)
- ✅ Runs tests and linting
- ✅ Bumps version in all files
- ✅ Commits and pushes version bump
- ✅ Creates and pushes git tag
- ✅ Updates Homebrew formula
- ✅ Upgrades local brew installation
- ✅ Verifies everything works
After this script completes, your system is running the new version!
Examples
# Release version 0.9.3
./scripts/release.sh 0.9.3
# Preview a release (no changes made)
./scripts/release.sh 1.0.0 --dry-run
Prerequisites
- Clean git working directory
- All changes committed
- golangci-lint installed
- Homebrew installed (for local upgrade)
- Push access to gastownhall/beads
Output
The script provides colorful, step-by-step progress output:
- 🟨 Yellow: Current step
- 🟩 Green: Step completed
- 🟥 Red: Errors
- 🟦 Blue: Section headers
What Happens Next
After the script finishes:
- GitHub Actions builds binaries for all platforms (~5 minutes)
- PyPI package is published automatically
- Users can
brew upgrade beadsto get the new version - GitHub Release is created with binaries and changelog
bump-version.sh
Bumps the version number across all beads components in a single command.
Usage
# Show usage
./scripts/bump-version.sh
# Update versions (shows diff, no commit)
./scripts/bump-version.sh 0.9.3
# Update versions and auto-commit
./scripts/bump-version.sh 0.9.3 --commit
What It Does
Updates version in all these files:
cmd/bd/version.go- bd CLI version constantplugins/beads/.claude-plugin/plugin.json- Claude plugin versionplugins/beads/.codex-plugin/plugin.json- Codex plugin version.claude-plugin/marketplace.json- Claude marketplace plugin versionintegrations/beads-mcp/pyproject.toml- MCP server versionREADME.md- Alpha status versionPLUGIN.md- Version requirements
Features
- Validates semantic versioning format (MAJOR.MINOR.PATCH)
- Verifies all versions match after update
- Shows git diff of changes
- Auto-commits with standardized message (optional)
- Cross-platform compatible (macOS and Linux)
Examples
# Bump to 0.9.3 and review changes
./scripts/bump-version.sh 0.9.3
# Review the diff, then manually commit
# Bump to 1.0.0 and auto-commit
./scripts/bump-version.sh 1.0.0 --commit
git push origin main
Why This Script Exists
Previously, version bumps only updated cmd/bd/version.go, leaving other components out of sync. This script ensures all version numbers stay consistent across the project.
Safety
- Checks for uncommitted changes before proceeding
- Refuses to auto-commit if there are existing uncommitted changes
- Validates version format before making any changes
- Verifies all versions match after update
- Shows diff for review before commit
sign-windows.sh
Signs Windows executables with an Authenticode certificate using osslsigncode.
Usage
# Sign a Windows executable
./scripts/sign-windows.sh path/to/bd.exe
# Environment variables required for signing:
export WINDOWS_SIGNING_CERT_PFX_BASE64="<base64-encoded-pfx>"
export WINDOWS_SIGNING_CERT_PASSWORD="<certificate-password>"
What It Does
This script is called automatically by GoReleaser during the release process:
- Decodes the PFX certificate from base64
- Signs the Windows executable using osslsigncode
- Timestamps the signature using DigiCert's RFC3161 server
- Replaces the original binary with the signed version
- Verifies the signature was applied correctly
Prerequisites
osslsigncodeinstalled (apt install osslsigncodeorbrew install osslsigncode)- EV code signing certificate exported as PFX file
- GitHub secrets configured:
WINDOWS_SIGNING_CERT_PFX_BASE64- base64-encoded PFX fileWINDOWS_SIGNING_CERT_PASSWORD- certificate password
Graceful Degradation
If the signing secrets are not configured:
- The script prints a warning and exits successfully
- GoReleaser continues without signing
- The release proceeds with unsigned Windows binaries
This allows releases to work before a certificate is acquired.
Why This Script Exists
Windows code signing helps reduce antivirus false positives that affect Go binaries.
Kaspersky and other AV software commonly flag unsigned Go executables as potentially
malicious due to heuristic detection. See docs/ANTIVIRUS.md for details.
Future Scripts
Additional maintenance scripts may be added here as needed.