release

Guild Release — snapshot and tag a version

Finalize completed guild requirements into a versioned release: stamp CHANGELOG.md's Unreleased section with a version, render the released requirements out of the database into a dated snapshot directory, record the release on the board, and create an annotated git tag.

Status is a column. There are no status directories and no ticket files — a release copies nothing and moves nothing; it renders. Load guild:warehouse before the first query.

export PATH="$HOME/.turso:$PATH"
DB=.guild/guild.db

Arguments

• --dry-run — print the full plan, write nothing, run no git command
• --only REQ-NNN[,REQ-MMM] — release only the named requirements (default: every done requirement not already recorded in a previous release)

Step 1 — preconditions

Run in parallel:

• git rev-parse --is-inside-work-tree — confirm a repo
• git status --short — uncommitted changes
• git tag --list --sort=-v:refname — existing tags
• [ -f .guild/config.yaml ] — confirm the guild exists

Stop conditions:

• Not a git repo → Not inside a git repository. Guild release requires git.
• No .guild/config.yaml → No guild found. Nothing to release.
• Uncommitted changes → ask, and default to stopping on "no":

  You have uncommitted changes. A release should be a clean point in history.
  Continue anyway? (yes / no)
  

Step 2 — what is in scope

A release is recorded on the board, in guild_state under release:<version>, so "what has already shipped" is a query rather than a directory scan:

SELECT r.id, r.title
  FROM requirement r
 WHERE r.status = 'done'
   AND NOT EXISTS (SELECT 1 FROM guild_state gs, json_each(gs.value, '$.requirements') j
                    WHERE gs.key LIKE 'release:%' AND json_valid(gs.value) AND j.value = r.id)
 ORDER BY r.id;

With --only, use exactly the named ids instead — and verify each is done before including it.

Empty set → stop with No completed requirements to release since the last release.