From 90ad9e632520d3bbc22562c0fd4db2584ef2a92c Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 15 Nov 2026 16:49:08 +0000 Subject: store: a signed value chosen by seq is named so Where the policy asks for signed values, a place's value is chosen by `seq`, but conflict reports still called the choice `newestWins`, and the code and the architecture still said "newest" of what a read shows. A report names it `highestSeq`; the rest says "the one a read shows". --- docs/openapi.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/openapi.yaml') diff --git a/docs/openapi.yaml b/docs/openapi.yaml index 5728da5..678cfe3 100644 --- a/docs/openapi.yaml +++ b/docs/openapi.yaml @@ -2173,7 +2173,7 @@ components: description: On the way to the requested path (candidates without values). resolution: type: string - enum: [mergedMaps, newestWins] + enum: [mergedMaps, newestWins, highestSeq] candidates: type: array items: -- cgit v1.3.1