The plan
bsm.plan is the single source of deploy order.
bsm.plan# comments start with #
create-customer @2026-11-03T14:10Z brock # a note
add-customer-email [create-customer] @2026-11-04T09:02Z alice
rebuild-fulltext [create-product] !notx @2026-11-04T09:15Z bob
drop-legacy !irreversible @2026-11-05T08:00Z alice
@release-1.4
Line syntax
| Part | Meaning |
|---|---|
name | The change; matches changes/name/. |
[a b] | Changes this one requires. They must appear earlier in the plan. |
!notx | Run outside a transaction (see Changes). |
!irreversible | No revert script; revert stops here with an explicit error. |
@timestamp author | When and by whom it was planned. Informational, not hashed. |
# note | A note. Not hashed. |
@tag (own line) | Tags the change above it. Use as --to @tag. |
bsm add and bsm tag write these lines for you. The name, dependencies and flags are part of the change's hash; notes, authors and timestamps are not.
Why one change per line
When two developers each append a change on their branches, git's union merge driver keeps both lines instead of reporting a conflict. bsm init adds the rule to .gitattributes:
bsm.plan merge=union
Run bsm plan check after merging. It catches the cases a union merge cannot judge: the same name added twice, a dependency on a change that was removed, or a folder without a plan line. See Teams and ordering.
Targets
--to accepts a change name or a tag: bsm deploy --to @release-1.4 deploys up to and including the tagged change.