github gastownhall/beads v1.4.0-rc.3

pre-release55 minutes ago

beads v1.4.0-rc.3

Pre-compiled binaries for Linux, macOS (Intel & Apple Silicon), Windows (AMD64 & ARM64), Android/Termux (ARM64), and FreeBSD.

Installation (release candidate)

This is a prerelease for validation. The stable install channels —
Homebrew, the install.sh / install.ps1 scripts, npm, and PyPI —
intentionally keep serving the latest stable release, so they will not
install this RC. Use one of the methods below.

Manual download (recommended):
Download the archive for your platform from the Assets below, extract it,
and place bd on your PATH.

Go install (pinned to this RC):

go install github.com/steveyegge/beads/cmd/bd@v1.4.0-rc.3
# For embedded Dolt support:
CGO_ENABLED=1 GOFLAGS=-tags=gms_pure_go go install github.com/steveyegge/beads/cmd/bd@v1.4.0-rc.3

1.4.0 is a one-way upgrade. Back up first. Consenting to the schema migration (bd migrate schema, --force, or BD_ALLOW_MIGRATE=1) moves a 1.2.x or 1.3.x store to schema v74. After that, bd 1.3.x and older refuse the database; going back means restoring a backup. From 1.4.0-rc.1 or rc.2, rc.3 is a binary swap: it adds no migration.

  • Validate on a copy, or on a store you have backed up with your current bd (bd dolt push, a JSONL export, or bd backup sync).
  • Every Dolt server bd talks to, and the dolt CLI on PATH, must be 2.6.0 or newer.
  • Read Upgrade notes and Known issues under [1.4.0-rc.3], [1.4.0-rc.2] and [1.4.0-rc.1] in CHANGELOG.md before installing.

New in rc.3:

  • Telemetry no longer exports issue content. Correction to the rc.1 notes: with the console trace exporter on (BD_OTEL_ENABLED=true with OTEL_TRACES_EXPORTER=console, or the legacy BD_OTEL_STDOUT=true on its own), rc.1 and rc.2 still wrote titles, descriptions, notes, labels, comments and search text to stderr in the bd.args span attribute (#8505); logs that kept bd's stderr can hold it. bd.args now names only the command and the flags that were set, so trace queries that read its values must change.
  • bd ranks a release candidate below its release (#6595), and in server and proxied-server workspaces moving from a candidate to 1.4.0 records the release in the version marker. From rc.3 on, server-mode bd doctor run in a terminal reports when 1.4.0 is out.

Behavior changes to know before installing (from rc.2):

  • bd github now stops when a repository lookup fails. Rerun after a temporary failure. Never clear or repoint another repository's bead links to get past it: the next sync creates unlinked beads as new issues in the configured repository.
  • Server-mode pulls need EXECUTE on dolt_fetch and dolt_merge.
  • bd backup restore refuses a Dolt server on another host. Run it on the server's machine, in a workspace that names the same dolt_database.

Still open:

  • #7283: in server mode, run bare bd migrate once per database if bd doctor reports a version mismatch after bd migrate schema.
  • Go programs that link beads cannot open a proxied-server workspace (#8412, #8323).
  • bd create --repo <url>'s cached clone still writes the URL into merge commits (#8434).

When 1.4.0 ships, install it by hand. rc.3's server-mode bd doctor, run in a terminal, also tells you; nothing tells you on rc.1 or rc.2, on an embedded or proxied-server workspace, or when bd doctor runs under an agent, a script or --json.

Changelog

Bug Fixes

  • b35d1bb fix(doctor): give CompareVersions semver-2.0 prerelease semantics (#6596)
  • e16aa3f fix(telemetry): keep issue content out of bd.args (#8505) (#8508)
  • 93aa92d fix(version): a release records its version over its own release candidate (#8511)

Others

  • d42ff8d chore(release): prepare v1.4.0-rc.3

Don't miss a new beads release

NewReleases is sending notifications on new releases.