* docs: generate CLI reference from live help * docs(cli): move bd version stamp from per-command pages to index only Drops the `(bd version X.Y.Z)` suffix from the auto-generated header on every per-command CLI reference page (writeSingleCommandDoc) and the docs/CLI_REFERENCE.md preamble (writeAllHelp). The version label now lives only on the index page emitted by scripts/generate-cli-docs.sh: - Dev tree (website/docs/cli-reference/index.md, docs/CLI_REFERENCE.md): labelled "Latest" - Versioned snapshots (website/versioned_docs/version-X.Y.Z/...): labelled with the explicit semver tag parsed from the directory name This eliminates the 100+-file no-signal diff a release version bump otherwise produces, restoring the "regen as a separate small commit" workflow PR #3704 enables. After this change a version bump alone yields zero diff on the dev tree; only the new versioned snapshot created at release-cut time carries the new tag. No datestamps are introduced anywhere — scripts/generate-cli-docs.sh --check remains deterministic across CI runs. Refs: mybd-afb, PR #3704 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: CI Bot <ci@beads.test> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
76 lines
1.7 KiB
Markdown
76 lines
1.7 KiB
Markdown
---
|
|
id: upgrade
|
|
title: bd upgrade
|
|
slug: /cli-reference/upgrade
|
|
sidebar_position: 999
|
|
---
|
|
|
|
<!-- AUTO-GENERATED: do not edit manually -->
|
|
Generated from `bd help --doc upgrade`
|
|
|
|
## bd upgrade
|
|
|
|
Commands for checking bd version upgrades and reviewing changes.
|
|
|
|
The upgrade command helps you stay aware of bd version changes:
|
|
- bd upgrade status: Check if bd version changed since last use
|
|
- bd upgrade review: Show what's new since your last version
|
|
- bd upgrade ack: Acknowledge the current version
|
|
|
|
Version tracking is automatic - bd updates metadata.json on every run.
|
|
|
|
```
|
|
bd upgrade
|
|
```
|
|
|
|
### bd upgrade ack
|
|
|
|
Mark the current bd version as acknowledged.
|
|
|
|
This updates metadata.json to record that you've seen the current
|
|
version. Mainly useful after reviewing upgrade changes to suppress
|
|
future upgrade notifications.
|
|
|
|
Note: Version tracking happens automatically, so you don't need to
|
|
run this command unless you want to explicitly mark acknowledgement.
|
|
|
|
Examples:
|
|
bd upgrade ack
|
|
bd upgrade ack --json
|
|
|
|
```
|
|
bd upgrade ack
|
|
```
|
|
|
|
### bd upgrade review
|
|
|
|
Show what's new in bd since the last version you used.
|
|
|
|
Unlike 'bd info --whats-new' which shows the last 3 versions,
|
|
this command shows ALL changes since your specific last version.
|
|
|
|
If you're upgrading from an old version, you'll see the complete
|
|
changelog of everything that changed since then.
|
|
|
|
Examples:
|
|
bd upgrade review
|
|
bd upgrade review --json
|
|
|
|
```
|
|
bd upgrade review
|
|
```
|
|
|
|
### bd upgrade status
|
|
|
|
Check if bd has been upgraded since you last used it.
|
|
|
|
This command uses the version tracking that happens automatically
|
|
at startup to detect if bd was upgraded.
|
|
|
|
Examples:
|
|
bd upgrade status
|
|
bd upgrade status --json
|
|
|
|
```
|
|
bd upgrade status
|
|
```
|