The dv v1 <package> command exists (commit 06cc1de) but has not yet been exercised against @dv-cli/dv itself, pending an audit pass of the remaining v1 commands.
The ceremony was rehearsed against this repo on 2026-05-25:
dv migrate config --dry-run reports already-current shapedv version --dry-run projects the pending Recordsdv v1 @dv-cli/dv --dry-run --yes projects → 1.0.0 with @dv-cli/clipc's constraint rewrittendv plugin verify against the deno example reports pass
The real promotion is left as a deliberate next step rather than an autonomous one — 1.0 is one-way.
We tried promoting once and walked it back (revert of a9a32c1) because the use-key redesign became visible during the ceremony. That redesign + its migration command have since landed, so the "breaking changes before 1.0" list is empty. The ceremony can rerun once the remaining v1 commands are audited.
Migrated from ROADMAP.md § Pre-1.0 work still to do / Start here.
The
dv v1 <package>command exists (commit06cc1de) but has not yet been exercised against@dv-cli/dvitself, pending an audit pass of the remaining v1 commands.The ceremony was rehearsed against this repo on 2026-05-25:
dv migrate config --dry-runreports already-current shapedv version --dry-runprojects the pending Recordsdv v1 @dv-cli/dv --dry-run --yesprojects →1.0.0with@dv-cli/clipc's constraint rewrittendv plugin verifyagainst the deno example reports passThe real promotion is left as a deliberate next step rather than an autonomous one — 1.0 is one-way.
We tried promoting once and walked it back (revert of
a9a32c1) because the use-key redesign became visible during the ceremony. That redesign + its migration command have since landed, so the "breaking changes before 1.0" list is empty. The ceremony can rerun once the remaining v1 commands are audited.Migrated from ROADMAP.md § Pre-1.0 work still to do / Start here.