docs(adr): propose ADR-0018 Ploeg releases on its own schedule behind a tested contract version #183
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ryangr0/adr-ploeg-independent-releases"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The owner allowed Ploeg to release independently on 2026-10-03 and asked
what happens with incompatibility. ADR-0018 proposes to supersede ADR-0004's
single version: Ploeg and Vloer get their own release trains, Ploeg's
operator API carries a MAJOR.MINOR contract version (a /version route and a
Ploeg-Contract header), and Vloer declares the range it supports. Outside
that range, Vloer shows a blocking banner and makes no managed calls.
Contract changes are expand and contract, with a proposed 60-day
deprecation window. A cross-version qualification of real Ploeg and real
Vloer gates releases. An unfold-v bundle pins a qualified pair, and the
joint draft barrier from #146 moves to that bundle. The ADR lists five
owner questions and eight follow-up tickets. No code changes.
Proposed, not accepted. Five owner questions are marked in the ADR (banner vs refuse to start, deprecation window, automatic bundles, Vloer's own train, contract scope). On acceptance it supersedes ADR-0004 and eight follow-up tickets get filed.
Verified with
mise run verifyon the pinned toolchain (all gates passed).Ticket: https://vikunja.webgrip.dev/tasks/1756
🤖 Generated with Claude Code