---
{
  "n": 33,
  "title": "Cutting a patch release",
  "abstract": "",
  "refs": [],
  "seen": [
    "system",
    "agent"
  ],
  "data": {
    "starts_on": "",
    "system": true,
    "environment": "main",
    "unless": {},
    "started_by": "",
    "only_when_idle": false,
    "talks_in": "",
    "lasting": false,
    "dispatch": "",
    "runs": {}
  },
  "created": 1791661433.058254,
  "updated": 1791670456.247205,
  "deleted": 0.0,
  "completed": 0.0,
  "outcome": "",
  "type": "sequence"
}
---
Fixes that were taken and tested go out at once as a patch; features wait for the next minor.

## Check what goes in
Only fixes whose tests ran and passed go into a patch: journal helper peers and journal todo all show what was taken since the last release. Leave a feature and anything untested for the next minor. Then journal sequence next <this sequence> --about <ref>.

## Bump and note it
Raise the patch number where the project keeps its version, add a line to its changelog for each fix, and commit both with a message that names the fixes. Then journal sequence next <this sequence> --about <ref>.

## Tag and push
Tag the version and push it the way the project releases, with its own command or gate if it has one. A fix for a project that runs on the journal is released at once, without the whole suite. Then journal sequence next <this sequence> --about <ref>.

## Tell the user
Say in one plain line which version went out and what it holds, naming each fix with its row. Finish with journal sequence next <this sequence> --about <ref>.