ADR-0027's Context describes the CI chain as:
The stellar-api CI chain (.github/workflows/publish.yml) runs test → smoke → publish
That was accurate when written (2026-07-09). It no longer is — the chain has gained two jobs since:
Scope: description, not decision
The decision stands and is not in question. ADR-0027 decides that this repo's pipeline ends at publish and that deployment belongs to stellar-compose. The release job does not violate that — it publishes a record of the artifact, not a deployment, and touches no environment.
What is stale is the factual description of the pipeline in the Context section, plus the closing line "The v0.7.0 CI/CD picture is complete: build → verify → publish here" which reads as a full enumeration.
Why bother
An ADR's Context is what the next reader trusts to know the current shape of things without reading the YAML. This one now under-describes the chain by two jobs, one of which (release) is the newest and least obvious. It is the cheap kind of drift that makes the expensive kind plausible.
A short amendment in the ADR's own amendment style is enough — the same treatment ADR-0024 and ADR-0026 received when their surroundings moved. Do not rewrite the Context in place: the ADR is the record of what was true when the decision was made.
Related
docs/runbooks/release.md documents the current chain correctly, so the two would disagree until this lands.
Found during a repo sweep (Phase 9 reconcile, claims diff).
ADR-0027's Context describes the CI chain as:
That was accurate when written (2026-07-09). It no longer is — the chain has gained two jobs since:
integration— split out oftestin perf(hooks): cut pre-commit chain runtime (~8.5 min full chain) #306 so the DB-bound suite runs in parallel; both are required checks.release— added by ci(release): create GitHub Releases from the CHANGELOG on tag push #383; tag-only,needs: [publish], creates the GitHub Release from the CHANGELOG section.Scope: description, not decision
The decision stands and is not in question. ADR-0027 decides that this repo's pipeline ends at publish and that deployment belongs to stellar-compose. The
releasejob does not violate that — it publishes a record of the artifact, not a deployment, and touches no environment.What is stale is the factual description of the pipeline in the Context section, plus the closing line "The v0.7.0 CI/CD picture is complete: build → verify → publish here" which reads as a full enumeration.
Why bother
An ADR's Context is what the next reader trusts to know the current shape of things without reading the YAML. This one now under-describes the chain by two jobs, one of which (
release) is the newest and least obvious. It is the cheap kind of drift that makes the expensive kind plausible.A short amendment in the ADR's own amendment style is enough — the same treatment ADR-0024 and ADR-0026 received when their surroundings moved. Do not rewrite the Context in place: the ADR is the record of what was true when the decision was made.
Related
docs/runbooks/release.mddocuments the current chain correctly, so the two would disagree until this lands.Found during a repo sweep (Phase 9 reconcile, claims diff).