---
name: release-standard-bump-in-pr
description: "Release process standard v0.14.1 onward — bump rides in the release PR, tag on merge gated on green PR run"
metadata: 
  node_type: memory
  type: project
  originSessionId: eb2b5080-21d0-44ab-b08e-f5d1c9f2092f
---

NEW RELEASE STANDARD (operator-directed via doyle, 2026-06-23), applies **v0.14.1 ONWARD**.

**Change:** STOP authoring the version bump as a separate direct-push to main and waiting for a second full `push:[main]` CI pass before tagging. That re-runs the whole ~11min × 2-runner suite on byte-identical code (only version string + CHANGELOG + first-party Cargo.lock lines changed) — pure latency.

**New flow (v0.14.1+):**
1. Put the bump IN the release PR — the feature PR's final commit, OR a dedicated release PR when the work already merged. Bump = `Cargo.toml` workspace.package.version + `Cargo.lock` first-party `spt-*` lines + CHANGELOG section + `xtask gen` regen.
2. The PR's CI validates the EXACT commit that gets tagged.
3. On merge → tag straight away, gated on the green PR run.
4. The merge still fires `push:[main]` CI automatically — let it run as a NON-BLOCKING backstop; do NOT wait for it to tag.

Net: removes the serial second-CI wait.

**v0.14.0 was the LAST cut under the old flow** (separate bump-push to main @6ba875e + second push:[main] CI before tag) — finished as-is, not retro-changed. doyle is encoding this in `docs/RELEASE-RUNBOOK.md` (PR).

Relates to [[v0140-endpoint-creation-flow]]. Publisher discipline (counter-from-`.release.json`, first-party-Cargo.lock-only, doyle CHANGELOG-vet) unchanged.