* test(bazel): shard http_served_test and corpus_served_test (embedded lane critical path) Both served targets ran as one shard each (235-597s) and were the embedded lane's longest action in most executing runs; every other embedded shard ends by ~90-155s. - http_served_test runs through go_test_pinned_shard.sh like httpclient_served_test: the 19 TestE2E_* cases >= 3s are pinned onto 6 shards (pin_shards.py from three lane runs' test.xml plus one local run, <= ~88 measured seconds each), the ~28 fast tests round-robin in a 7th. - corpus_served_test: TestServedCorpus becomes TestServedCorpusPart1..4. Shapes are dealt round robin in corpus order; each part starts its own server and seeds its own pair of workspaces. The shapes are independent: every check is served-vs-embedded parity after the same commands, each write owns its target ids, and order preservation keeps each part's reads ahead of its writes. TestCorpusPartsDealEveryShapeOnce checks the deal (every shape once, in order, no empty part); the manifest pins part k to shard k, with a 5th round-robin shard for the engine-free tests, and scripts TestCorpusPartsArePinnedOnePerShard ties corpusParts, the manifest and shard_count together. BEADS_CORPUS_REPORT now accumulates every part the process ran. - pinnedShardTargets and the retired-lane args pins list both targets; go_test_sources_test gets the two packages' manifests as data. Embedded goes from 172 to 182 test actions; the dolt-race/dolt-int union budgets do not include the embedded tag and are unchanged. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * test(corpus): seed the served and embedded sides concurrently in each part Each TestServedCorpusPartN paid the server start and both seeds serially (about 100-150s of a 190-220s shard in #7537's CI). The embedded side now runs bd init and the seed on a goroutine while the test goroutine starts the server and proxy and seeds the served side. - prepareSide attaches one side (connect or init), writes its assets and runs the seed in order, returning failures as errors (execBD, runBD without the testing.T) so it is safe off the test goroutine; a failing side cancels the other, and a deferred cancel+Wait keeps the goroutine from outliving the test or its TempDirs. - The sides share no directory, env or bd process; shapes, their order and every assertion are unchanged. Each part logs its setup time. - bazel.yml's embedded lane uploads the served targets' test.xml on every run (bazel-embedded-served-testxml), so their pinned shards can be sized from a sharded run of the lane. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * test(bazel): corpus in 3 parts; re-pin http_served_test from a sharded CI run Measured on this PR's first embedded-lane run (test.xml from the new bazel-embedded-served-testxml artifact): - corpus_served_test with concurrent seeding: parts 1-4 ran 135/140/144/114s, of which setup (part time minus its shapes) was 76/76/76/62s and the 127 shapes 242s together. The setup floor is still ~70s+, so corpusParts goes from 4 to 3 (round robin; the measured split is 85/81/76s of shapes) and the manifest and shard_count follow (4 shards: 3 parts + round-robin). - http_served_test: #7537's pins were sized from single-shard runs, and the sharded shards ran 73-184s against ~88s estimated. served_pinned_shards.txt is regenerated with pin_shards.py from that sharded run's per-test durations: 119/118/120/128/132/123 measured seconds per pinned shard. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * test(bazel): pin http_served_test on the max over two sharded CI runs The second run of the lane on this PR ran the same tests at 0.2-1x their first-run times (executor load, not the tests), and its re-pinned shards came out 36-118s against 118-132s estimated. pin_shards.py now takes each test's maximum over both runs' test.xml, the same rule the other pinned targets use: 123-135 measured seconds per pinned shard. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * test(corpus): guard part wiring; seed metadata on e2e-t-ifa (review of #7537) - testServedCorpus fails (before the engine gate, so in every lane) unless the test's name is TestServedCorpusPart<part>: a TestServedCorpusPart3 calling testServedCorpus(t, 2) would run part 2 twice and silently drop part 3's shapes. TestCorpusPartNameMustMatchItsPart covers the check and that servedCorpusParts lists Part1..N in order. Mutation (Part3 -> 2) fails //backend/http/corpus:corpus_test with "TestServedCorpusPart3 runs corpus part 2; only TestServedCorpusPart2 may". - e2e-t-ifa is seeded with metadata seeded=keep. The parts seed separately, so the two refused (exit 13) conditional updates no longer always follow gc-update-if-assignment's k=v; their verify show again holds that a refusal keeps existing metadata. Mutation (served verify output's seeded=keep rewritten) fails both stale shapes at $[0].metadata.seeded. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * test(bazel): back to 4 corpus parts (served long pole over test-seconds) maintainer-city-c3's call on the measured trade-off. With concurrent seeding, 4 parts ran 114-146s each (run A) and 3 parts ran 170-180s (run D). 3 parts save one ~75s setup, about 75 test-seconds per executing run, but the longest part is the embedded lane's served long pole. That pole is on the gate's critical path (forks' above all), and 4 parts cut it by ~34s. corpusParts=4, TestServedCorpusPart4, manifest part 4 on shard 4, shard_count=5. The part-name guard is unchanged and covers Part4. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * ci(bazel): served-timings upload is telemetry; corpus part bounds and ctx Review of #7538 (maintainer-city-c3): - "Upload served test timings" gets continue-on-error: true and timeout-minutes: 2, like the CI analytics upload. An artifact-service 5xx or stall no longer fails the required embedded lane or holds it until the job timeout. TestBazelWorkflowSecretsAndFailureSurface allows that continue-on-error only on this exact step (bazelServedTimingsContinueOnErrorPath, which also pins its name, artifact, path and timeout; TestBazelEmbeddedServedTimingsUploadIsTelemetry). - corpusPartNameErr also refuses a part outside 1..corpusParts, so a stray TestServedCorpusPart5 fails instead of running no shapes. Two new cases. - expand takes ctx: prepareSide's {rev:} lookups run under the seeding context, so a cancel stops them as well. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| bench-ready-indexes | ||
| check-versions | ||
| checkworkflowtags | ||
| ci | ||
| gitattributespolicy | ||
| hooks | ||
| internal/testbash | ||
| migration-test | ||
| pr-lint | ||
| prlintmake | ||
| repochecks | ||
| repro-be-1he-slow-path | ||
| repro-dolt-hang | ||
| repro-dolt-prod-timeouts | ||
| workflowtags | ||
| bazel-autofix-push.sh | ||
| bazel_autofix_push_test.go | ||
| bazel_cache_mode_test.go | ||
| bazel_dolt_int_test.go | ||
| bazel_dolt_race_test.go | ||
| bazel_farm_workflow_test.go | ||
| bazel_fork_mode_test.go | ||
| bazel_go_repository_tools_test.go | ||
| bazel_hermetic_cc_test.go | ||
| bazel_invocations_test.go | ||
| bazel_policy_test.go | ||
| bazel_rbe_prewarm_test.go | ||
| bazel_rrc_test.go | ||
| bazel_skip_allowlist_test.go | ||
| build-examples.sh | ||
| BUILD.bazel | ||
| bump-version.sh | ||
| check-build-tags.sh | ||
| check-cli-docs-drift.sh | ||
| check-doc-flags.sh | ||
| check-doc-freshness.sh | ||
| check-go-install-guidance.sh | ||
| check-migration-hygiene.sh | ||
| check-testing-short.sh | ||
| check-versions.sh | ||
| check-winget-portable-alias.sh | ||
| check-workapi-frontend-boundary.sh | ||
| check_build_tags_test.go | ||
| check_doc_freshness_test.go | ||
| check_release_cross_compile_test.go | ||
| check_testing_short_test.go | ||
| check_winget_portable_alias_test.go | ||
| ci_actions_policy_test.go | ||
| ci_analytics_extract_test.go | ||
| ci_analytics_workflow_test.go | ||
| ci_blacksmith_runner_test.go | ||
| ci_f7b_review_test.go | ||
| ci_f7c_advisory_test.go | ||
| ci_merge_queue_test.go | ||
| ci_workflow_apt_get_timeout_test.go | ||
| ci_workflow_core_test.go | ||
| ci_workflow_test.go | ||
| clean-test-tmp.sh | ||
| complexity_script_test.go | ||
| conformance.sh | ||
| conformance_script_test.go | ||
| cross-version-smoke-test.sh | ||
| docs-autofix-push.sh | ||
| docs.md | ||
| embedded_shard_count_test.go | ||
| gen-winres.sh | ||
| generate-cli-docs.sh | ||
| generate-newsletter.py | ||
| generate-newsletter_README.md | ||
| gh-body-lint | ||
| host_tool_exec_policy_test.go | ||
| host_tool_shell_policy_test.go | ||
| host_tools_test.go | ||
| install-hooks.sh | ||
| install.sh | ||
| install_dolt_test.go | ||
| makefile_bazel_primary_test.go | ||
| managed_local_lane_test.go | ||
| migrate-jsonl-to-dolt.sh | ||
| migrate-legacy-to-current.sh | ||
| migration_corpus_bazel_test.go | ||
| mutation-equivalence.sh | ||
| nogo_integration_scan_test.go | ||
| nogo_integration_step_script_test.go | ||
| nogo_lint_policy_test.go | ||
| pinned_shards_helpers_test.go | ||
| pinned_shards_sources_test.go | ||
| pinned_shards_test.go | ||
| pr-preflight.sh | ||
| pr_lanes_bazel_coverage_test.go | ||
| pr_preflight_test.go | ||
| pr_risk_bazel_coverage_test.go | ||
| pre-push-suite.sh | ||
| pre_push_suite_test.go | ||
| proxied_lane_coverage_test.go | ||
| pull_dolt_image_test.go | ||
| rbe_worker_env_test.go | ||
| README.md | ||
| release.sh | ||
| release_script_test.go | ||
| repo_helpers_test.go | ||
| required_suite_test.go | ||
| resolve-docs-bd.sh | ||
| scripts_targets_test.go | ||
| shard_manifest_test.go | ||
| sign-windows.sh | ||
| test-cgo.sh | ||
| test-git-remote.sh | ||
| test-icu-path.sh | ||
| test.sh | ||
| test_script_test.go | ||
| testing_short_tree_test.go | ||
| tracked_files_test.go | ||
| update-nix-vendorhash.sh | ||
| update-versions.sh | ||
| update-winget.sh | ||
| upgrade-smoke-test.sh | ||
| upgrade_smoke_loop_test.go | ||
| verify-cgo.sh | ||
| worker_env_autosync_test.go | ||
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-lint
make ci-package-mcp
make ci-package-npm
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.
ci-pr-lint keeps its supported Bash/Make entrypoint but delegates to the
checkout-owned scripts/pr-lint Go driver, which runs nogo (//tools/nogo)
under Bazel natively and cross-configured for windows/amd64 and darwin/arm64
(see engdocs/LINTING.md). This is the same shell-free
lint authority used by bd preflight in a Beads source checkout.
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-go 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.
scripts/check-testing-short.sh (make check-testing-short; CI runs it in
//scripts:go_sources_test) 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.
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.
Base-branch health is supplemented by a warn-only PR-gate sample: the last 60
completed pull_request-event runs, grouped per workflow. A single workflow
whose decisive runs (>= 5, across >= 3 distinct head branches) are all
failure-class is reported as a broken PR gate — the case where a job that
exists only in the PR workflow is red for every PR while the base branch shows
green. This detector never blocks (deliberately: automation classifies
unrecognized [block] lines as genuine merge blockers and would park merge
lanes on a false positive); it is skipped entirely while the base branch is
red.
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
- ✅ Verifies or opens the Homebrew core formula PR
- ✅ Upgrades local Homebrew 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
- 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
- Homebrew core formula is verified or tracked through its canonical PR
- Users can
brew upgrade beadsto get the new version after Homebrew merges - 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/reference/antivirus.md for details.
Future Scripts
Additional maintenance scripts may be added here as needed.