docs: drop the now-fixed flatten/allOf 3.1 exclusive-bounds caveat

reuvenharrison · claude · reuvenharrison · commit b1f85523af4e · 2026-05-03T21:06:37.000+03:00
The "flatten of allOf ignores 3.1 numeric exclusiveMinimum / exclusiveMaximum" caveat (issue #868) is fixed by this same PR's changes to flatten/allof/merge_allof.go: the merge now collects 3.1 numeric exclusive bounds alongside `minimum`/`maximum`, picks the most restrictive across both forms, and emits the result back in the form the winning bound came from. With that fix in place, the only remaining flatten-specific caveat section is empty, so the section header goes too. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
diff --git a/docs/OPENAPI-31.md b/docs/OPENAPI-31.md
@@ -47,10 +47,6 @@ The following 3.1 features are not yet fully supported by [`kin-openapi`](https:
 - **`$dynamicRef` / `$dynamicAnchor`**: parsed but not resolved during loading. Schemas using dynamic references for recursive definitions will not be followed.
 - **`pathItems` in `components`**: not represented in the parser's data model. Specs that declare reusable path items in components will silently drop them.
 
-The `flatten` command has one additional caveat:
-
-- **`flatten` of `allOf` ignores 3.1 numeric `exclusiveMinimum` / `exclusiveMaximum`**: when merging `allOf` subschemas, the merge logic considers only `minimum` / `maximum` and the 3.0-style boolean `exclusiveMinimum` / `exclusiveMaximum`. 3.1 numeric exclusive bounds are silently dropped from the merged result. Tracked in [#868](https://github.com/oasdiff/oasdiff/issues/868).
-
 If you hit any of these, please [open an issue](https://github.com/oasdiff/oasdiff/issues/new?template=bug_report.md&title=[3.1]%20).
 
 ## Feedback
