The v1.2.0 bump (fa3d8cc5c) reddened main: the tracked .githooks/* managed
sections embed the binary Version in their BEGIN/END markers, and
TestTrackedManagedHookSectionsMatchGenerator (added with the sections in
#5522) holds them byte-equal to the cmd/bd/hooks.go generator — but
update-versions.sh's hook step was a stale comment saying there were no
hook files to update (true of the old cmd/bd/templates/hooks/*, not of the
tracked rendered copies). update-versions.sh now rewrites the marker
version wholesale (not from CURRENT_VERSION — the markers were already
drifted at v1.1.0 when the 1.2.0 bump ran), and check-versions.sh gates
the markers so a bump that skips them is refused before the push instead
of reddening main after it.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The release workflow's MCP package gate runs 'uv sync --locked', but
update-versions.sh bumped integrations/beads-mcp/pyproject.toml without
regenerating uv.lock, and no pre-tag gate checked the lock. The stale
lock therefore only surfaced in the tag-triggered release run — after
the tag existed and could no longer be rewritten. This cost v1.1.0 and
v1.1.2 their first release runs and burned the v1.1.1 tag outright.
Two-part fix:
- update-versions.sh runs 'uv lock' as part of the bump when uv is
available, warning loudly (without aborting the bump half-applied)
when uv is missing or the lock fails.
- check-versions.sh gains a dependency-free check that the beads-mcp
version pinned in uv.lock matches the canonical version (PEP 440
normalization applied for -rc.N prereleases), plus a fuller
'uv lock --check' freshness pass when uv is available. Both the
release-tag pre-push hook and CI's verify-version-consistency job
run this script, so a stale lock is now refused before a tag exists.
Agent-Signature: claude-fable-5-xhigh on behalf of matt wilkie
Claude-Session: https://claude.ai/code/session_01HmGSvX14yJcKD8Ezw7qZwd
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
- beads-release formula: drop the snapshot-docs step (ran the deleted
scripts/snapshot-release-docs.sh on the critical needs-chain); stamp-
changelog now needs update-vendorhash
- update-versions.sh: remove the mangled --skip-docs/docs-snapshot logic
and garbled usage text left by mid-line deletions
- pre-push hook: drop the snapshot-script remediation hint
- release.yml: collapse the prerelease branch; BEADS_REQUIRE_RELEASE_DOCS
has no consumer since check-docs-version.sh was deleted
- RELEASING.md / scripts/docs.md: describe the current pipeline (no
--versioned, no website/ outputs, no check-docs-version.sh)
- docs-mintlify.yml: paths filter now includes engdocs/** and the curated
root markdown files the docsync guard validates
- docs-render-check.sh: pin mint@4.2.687, fail closed when mint dies
without producing a broken-links report, parse report lines only, drop
dead extract_page_links(), fix the stale jq requirement; mint.sh pins
the same version
- nightly.yml: remove the deleted website measurement suite option
- CODEOWNERS: init-safety ADR gate follows the file to engdocs/adr/
- beads-docs skill: align with settled decision 6 — no pointer stubs,
moved pages get docs.json redirects; bd's printed paths are fixed at
the source
- CHANGELOG (edited line), FEDERATION-SETUP, README, examples, oracle-a,
.buildflags, gh-issue-to-pr formula: retarget moved-file references;
anchor the build/ gitignore pattern
Per the decision record: no parallel run and no cutover PR. Removes
website/ (including the four versioned doc snapshots — current-only
versioning; snapshots remain in git history), deploy-docs.yml,
generate-llms-full.sh (Mintlify serves llms.txt natively), the ci-website
package gate (Makefile target, scripts/ci/website.sh, the package-website
jobs and their aggregate-gate entries in pr.yml/main.yml/release.yml, the
ci-measurements suite, detect-package-gates wiring), and the release-time
docs snapshot flow (snapshot-release-docs.sh, check-docs-version.sh, their
call sites in update-versions.sh/check-versions.sh, RELEASING.md section
rewritten for the Mintlify reality).
Drift machinery now covers exactly the Mintlify artifacts:
check-cli-docs-drift.sh pathspecs/fingerprint, docs-autofix-push.sh
allowlist, and check-doc-flags.sh scans drop the website/llms paths. The
beads-docs skill's generated-content and verification sections updated to
the bd-generic + docsmint pipeline.
NOTE for merge time: if branch protection requires the 'Package Gate
(website)' check by name (rather than the aggregate gate), drop it from
the required checks or PRs will wait forever.
Gates: docsync PASS, generate-cli-docs.sh --check PASS, freshness PASS.
Re-lands the v1.1.0-rc.1 release prep so the candidate can be reviewed before
the tag is cut (#4476 auto-merged the original prep; #4477 backed it out).
Restores v1.1.0-rc.1 version metadata across all package manifests, the
prerelease-aware release workflow and version scripts (prerelease tags skip the
stable docs-snapshot requirement and stay off the stable Homebrew/PyPI/npm
channels), the CHANGELOG and cmd/bd/info.go entries, and regenerates uv.lock to
1.1.0rc1.
Beyond the straight re-land:
- fix(release): match the winres/manifest numeric PE versions on the base
version in update-versions.sh, so a later prerelease-to-different-base bump
does not silently leave them stale.
- docs(release): document the prerelease / release-candidate workflow in
RELEASING.md.
Agent-Signature: claude-opus-4-8-xhigh on behalf of matt wilkie
* revert: back out v1.1.0-rc.1 release prep
Reverts merge commit 427fdd0c85 from #4476 so the RC release prep can go back through maintainer review.
Agent-Signature: codex-gpt-5.5-xhigh on behalf of matt wilkie
* fix(mcp): sync uv.lock to reverted 1.0.5 version
The #4476 revert rolled integrations/beads-mcp/pyproject.toml back to
1.0.5 but left uv.lock pinned at 1.1.0rc1, so `uv lock --locked` (the
Package Gate (MCP) check) failed and the aggregate CI Gate went red.
Regenerate the lockfile so pyproject and uv.lock agree on 1.0.5.
Agent-Signature: claude-unknown-model-high on behalf of matt wilkie
Allow prerelease version bumps without promoting stable docs, keep Windows resource versions numeric for prerelease builds, and skip Homebrew/npm/PyPI publishing for prerelease tags while still producing GitHub prerelease artifacts.
Agent-Signature: codex-gpt-5.5-xhigh on behalf of matt wilkie
Root cause of the 1.0.5 incident: the beads-release formula's snapshot-docs
step is advisory prose, not enforced. A release can bump cmd/bd/version.go and
tag/push while skipping the Docusaurus snapshot, and nothing blocks publish, so
the drift only surfaces as a red main after artifacts ship.
Three layered guards:
A. Atomic bump — scripts/snapshot-release-docs.sh encapsulates the docs
snapshot (docusaurus docs:version + lastVersion + regenerate CLI/llms +
verify) as one idempotent unit. scripts/update-versions.sh now calls it so
version.go and the docs snapshot cannot diverge (escape hatch: --skip-docs).
The formula's snapshot-docs step now invokes the same script.
B. Pre-publish gate — release.yml gains a verify-version-consistency job that
checks the tag matches version.go and runs check-versions.sh. goreleaser
(and thus all downstream publish jobs) needs it; publish-pypi keeps its
always() decoupling from goreleaser but is hard-gated on the verify result.
Drift now blocks publish instead of redding main afterward.
C. Pre-push refusal — .githooks/pre-push runs check-versions.sh when a
refs/tags/v* tag is pushed and refuses on drift, catching it on the
developer's machine before CI. Installed via the existing core.hooksPath.
Verified: shellcheck clean; release.yml valid YAML; script guard paths and the
hook's branch/tag dispatch tested.
Refs: mybd-a5hn
Agent-Signature: claude-opus-4-8-medium on behalf of matt wilkie
- Run gofmt on files that drifted from canonical formatting
- Remove hook template file checks from check-versions.sh and
update-versions.sh — hooks are now generated dynamically by
cmd/bd/hooks.go using the Version constant from version.go
- Fix check-versions.sh error message to reference update-versions.sh
instead of deprecated bump-version.sh
Authored by: Aaron Lippold<lippold@gmail.com>
Signed-off-by: Aaron Lippold <lippold@gmail.com>
Executed-By: beads/crew/emma
Rig: beads
Role: crew
Add go-winres integration to embed legitimate PE resource metadata (company name,
product name, version, file description, copyright, and application manifest) into
Windows binaries. AV heuristic engines check for PE metadata as a trust signal --
its absence is one of the triggers for Go binary false positives like Kaspersky
PDM:Trojan.Win32.Generic detection.
- Add cmd/bd/winres/ with PE version info config and app manifest
- Add scripts/gen-winres.sh to generate .syso resource files
- Update .goreleaser.yml before hooks to run gen-winres at build time
- Update release.yml CI to install go-winres
- Update version bump script to include winres metadata
- Update ANTIVIRUS.md documentation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The complex bump-version.sh script has been replaced with:
1. A deprecation notice pointing to the release molecule
2. A simpler update-versions.sh for quick local-only version bumps
For releases, use:
bd mol wisp beads-release --var version=X.Y.Z
The molecule provides guided, step-by-step release workflows with
proper handoffs and CI gates.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>