The v1.0.5 tag shipped with cmd/bd/version.go bumped to 1.0.5 but without the Docusaurus version snapshot, so check-version-consistency (via scripts/check-docs-version.sh) went red on main: versions.json and docusaurus.config.ts lastVersion were still 1.0.4 and website/versioned_docs/version-1.0.5 was missing. Create the 1.0.5 docs snapshot to restore consistency: - docusaurus docs:version 1.0.5 (versions.json + versioned_docs + sidebar) - set docusaurus.config.ts lastVersion to 1.0.5 - regenerate versioned CLI reference (stamps "Reference for bd v1.0.5") - regenerate website/static/llms-full.txt Verified: scripts/check-versions.sh and scripts/check-doc-flags.sh pass. Refs: mybd-4qku Agent-Signature: claude-opus-4-8-medium on behalf of matt wilkie
1 KiB
1 KiB
| id | title | slug | sidebar_position |
|---|---|---|---|
| ship | bd ship | /cli-reference/ship | 999 |
Generated from bd help --doc ship
bd ship
Ship a capability to satisfy cross-project dependencies.
This command:
- Finds issue with export:<capability> label
- Validates issue is closed (or --force to override)
- Adds provides:<capability> label
External projects can depend on this capability using: bd dep add <issue> external:<project>:<capability>
The capability is resolved when the external project has a closed issue with the provides:<capability> label.
Examples: bd ship mol-run-assignee # Ship the mol-run-assignee capability bd ship mol-run-assignee --force # Ship even if issue is not closed bd ship mol-run-assignee --dry-run # Preview without making changes
bd ship <capability> [flags]
Flags:
--dry-run Preview without making changes
--force Ship even if issue is not closed