DIXI Spec Kit documentation Español · Source on GitHub

/dixi.release

Purpose

Prepare release readiness evidence, changelog proposal and rollback plan.

Prepare the evidence for releasing the version in $ARGUMENTS, for a person to decide.

Generated by scripts/build-command-reference.py from the packaged command text; do not edit by hand.

Invocation

Argument: <version>. Angle brackets mark a required value and square brackets an optional one. In the steps, $ARGUMENTS is the text written after the command.

Example

The text after the command is the request; change it to match your project.

When to use it

Steps

  1. If no version is given, ask and stop.
  2. Run make verify and dixi check; collect the results, open tasks and proposed ADRs.
  3. Write docs/releases/<version>.md: included changes with their specs, verification evidence, known limitations, migration notes, rollback plan and a changelog proposal.
  4. List blockers explicitly. Do not tag, publish, approve a gate or deploy; those actions belong to the person and the pipeline.
  5. Suggest /dixi.review for the release changes.

Files read and written

Paths named by the command text:

Stops and human gates

Closing

Run dixi check before finishing and report: files touched, checks (run, failed, not run), open items and the suggested next command.

Next step