* release: prep v1.3.1-rc.1
Sanctioned RC bump per RELEASING.md "Cut an RC", on the #6298 model:
./scripts/update-versions.sh 1.3.1-rc.1, which carries the stamp into
version.go, the three plugin.json manifests, marketplace.json, the npm
package.json, the MCP pyproject.toml/__init__.py/uv.lock, default.nix,
the ten .githooks managed-section markers and the winres strings.
scripts/check-versions.sh passes all 24 gates at 1.3.1-rc.1.
Unlike the 1.3.0 RCs, this bump moves the BASE version, so
cmd/bd/winres/manifest.xml changes too (1.3.0.0 -> 1.3.1.0) along with
the winres numeric file_version/product_version (1.3.0 -> 1.3.1). Those
PE fields must be purely numeric; the FileVersion/ProductVersion strings
carry the full 1.3.1-rc.1, and uv.lock carries the PEP 440 normalization
1.3.1rc1 written by `uv lock`, never by hand.
This has to land before the tag: release.yml's verify-version-consistency
compares ${GITHUB_REF_NAME#v} byte-for-byte against the Version string in
cmd/bd/version.go, and every stamp on this branch still read 1.3.0.
Simulated against the working tree with the workflow's own grep/sed
pipeline: the extracted string is exactly "1.3.1-rc.1", on a single
matching line. The tag must be spelled v1.3.1-rc.1.
CHANGELOG: creates the [1.3.1] section dated 2026-09-16 and leaves
[Unreleased] empty but present, which is what #6038 (b3ef65c85) did when
it created [1.3.0] at branch-cut, and what #6298's fixup established for
an RC tag — an entry parked under [Unreleased] ships in no release by
Keep-a-Changelog semantics, yet the RC demonstrably ships it. The three
Fixed bullets already on the branch (#6580 x2, #6578) move under [1.3.1]
by the rename alone; their wording is untouched, and the shipped
[1.3.0] section and everything below it is byte-identical (sha256 of the
[1.3.0]-to-EOF region is unchanged across this commit).
The 2026-09-16 date is provisional. The final 1.3.1 prep must hand-restamp
it to the real release date rather than rerun the beads-release formula's
stamp-changelog step, which sed-inserts a fresh header under [Unreleased]
and never re-dates an existing section — running it against an already
dated [1.3.1] duplicates the heading. Same trap #6298 documented and #6564
then worked around.
cmd/bd/info.go: adds the 1.3.1-rc.1 digest at index 0 of versionChanges,
dated 2026-09-16 so the array stays newest-first with monotonic dates for
TestGetVersionsSinceOrder. It leads with the no-migration note (a 1.3.0
user's upgrade is a binary swap) and then digests the two #6580 changes and
the two #6578 ones. Per the #6298 lesson this key can only reach rc.1 users
by shipping inside the rc.1 binary; omit it and `bd upgrade review` dumps
the whole history at them.
docs/cli-docs.pin is still v1.2.2 on this branch — 1.3.0's docs-pin step
never happened. check-versions.sh explicitly excludes it, so it is not
tag-blocking and is deliberately left for the post-tag docs step.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* docs(release): reclassify 1.3.1 behaviour changes and document the config migration
Documentation-only amendment to the v1.3.1-rc.1 prep. No version stamp is
touched; ./scripts/check-versions.sh stays 24/24 at 1.3.1-rc.1.
Three corrections, all inside the `## [1.3.1]` section and its `cmd/bd/info.go`
`versionChanges` twin.
1. The flat->nested config migration is now documented (#6594). #6578 made
`bd config set <dotted.key>` write a nested mapping, and where a flat
top-level key of the same literal name exists it deletes that entry and
re-emits the value nested (`updateNestedYamlKey`). `.beads/config.yaml` is
not exclusively bd's, so another writer that reads its dotted keys flat
stops seeing any value migrated this way — and if it re-adds the flat key,
bd's own readers disagree: Viper-backed reads return the flat value while
GetStringFromDir returns the nested one. Verified both halves empirically
against this tree (dual-spelling probe: viper="flatvalue",
GetStringFromDir="nestedvalue", independent of document order; migration
probe: `dolt.host` flat entry deleted, sibling `dolt.port` and `other.thing`
byte-intact). Realistic collisions are `dolt.*`, `export.auto`,
`backup.enabled`.
2. Two genuine behaviour changes moved out of `### Fixed` into `### Changed`,
following the 1.3.0-rc.2 precedent in c1e5e49e3: the `bd dolt status --json`
shape change (#6580), which a parser of the old payload meets on upgrade,
and the two `bd config set` success->failure cases (#6578). The fix content
stays in `Fixed` with a pointer; neither statement appears in both sections.
3. `backend_endpoint` added to the documented key list in both CHANGELOG.md and
info.go. It is a real `omitempty` field on `proxiedDoltStatus`
(cmd/bd/dolt_proxied_lifecycle.go:63), set only when the sidecar reports an
external backend — the one topology where `backend_managed` is false and
nothing else names the server. Both surfaces now carry the same 11 keys as
the struct.
Validated: `## [1.3.0]`->EOF is byte-identical before and after
(sha256 798a2ee0b0f0b7a3f0fc017ae01c919807740348a34f5ea8719b82a008533d00);
exactly one `## [1.3.1]` heading, `## [Unreleased]` present and empty;
check-versions.sh 24/24; go build/vet ./...; go test ./cmd/bd -run
'TestGetVersionsSinceOrder|TestVersionChangesStructure|TestVersionChangesCoverage|TestVersionChangesJSON|TestGetVersionsSince|TestDisplayVersion'
all PASS, no skips; scripts/ci/pr-lint.sh and scripts/ci/pr-policy.sh green;
`bd info --whats-new` surfaces both amendments end-to-end.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>