docs(changelog): note the reinit destroy-token prefix fix (#6485)
Agent-Signature: claude-code-opus-5-5-unknown-reasoning on behalf of Harry Miller Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
269a92daba
commit
00a80bcc4c
1 changed files with 7 additions and 0 deletions
|
|
@ -692,6 +692,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|||
guard. `--recreate-missing` still opens it. The signal decision behind both
|
||||
guards is recorded in `engdocs/adr/0004-missing-database-guard-signal.md`.
|
||||
|
||||
- **Non-interactive `bd init --reinit-local` accepts `DESTROY-<issue-prefix>`
|
||||
without `--prefix`.** The local data-safety guard built its expected token
|
||||
from the raw `--prefix` flag, so with the prefix coming from config or the
|
||||
directory name it expected `DESTROY-` and refused the documented token with
|
||||
exit 12; it now uses the resolved prefix, as the remote-safety check already
|
||||
did (#6485).
|
||||
|
||||
- **`bd init --recreate-missing` now reaches its own opt-in.** The existing-data
|
||||
check derived "is this project's database here?" from the Dolt data
|
||||
directory, which exists on every initialized workspace, so the
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue