feat: add OpenAPI 3.1 support by reuvenharrison · Pull Request #1125 · getkin/kin-openapi

reuvenharrison · 2026-02-09T09:50:20Z

Summary

Comprehensive OpenAPI 3.1 / JSON Schema 2020-12 support. This consolidates and supersedes PRs #1102, #1114, #1118–#1124.

Core features

Type arrays with null support (e.g., ["string", "null"])
JSON Schema 2020-12 keywords: const, examples, prefixItems, contains, minContains, maxContains, patternProperties, dependentSchemas, propertyNames, unevaluatedItems, unevaluatedProperties
Conditional keywords: if/then/else, dependentRequired
Identity/referencing keywords: $id, $anchor, $dynamicRef, $dynamicAnchor
Content vocabulary: contentMediaType, contentEncoding, contentSchema
Core keywords: $schema, $comment, $defs
ExclusiveBound union type: supports both boolean (3.0) and numeric (3.1) exclusive bounds
BoolSchema type for unevaluatedItems and unevaluatedProperties: supports both boolean (false) and schema object forms, reusing the same pattern as AdditionalProperties
Webhooks with $ref resolution
Version detection: IsOpenAPI3_0(), IsOpenAPI3_1()
Info.Summary and License.Identifier fields

Validation

JSON Schema 2020-12 validator via EnableJSONSchema2020() (per-field) and EnableJSONSchema2020Validation() (document-level)
Auto-detection: doc.Validate() automatically enables JSON Schema 2020-12 mode for OpenAPI 3.1 documents
Built-in validator: const keyword enforcement, IsEmpty() awareness of all new fields
$ref resolution in loader for all new schema fields (including $defs)
Schema.validate() recursion into all new sub-schema fields
transformOpenAPIToJSONSchema recursion into all nested schemas (including $defs)
Allow $ref alongside other keywords (legal in 3.1)
Handle "null" type in schema validation

Backward compatibility

100% backward compatible with OpenAPI 3.0
ExclusiveBound transparently handles both boolean and numeric forms
BoolSchema reuses the existing AdditionalProperties pattern (type AdditionalProperties = BoolSchema alias preserves backward compatibility)
openapi2conv updated to convert between ExclusiveBound and boolean, preserving numeric bound values

Commit history

feat: add OpenAPI 3.1 support — base implementation (Types, Schema fields, Webhooks, JSON Schema validator, version helpers)
fix: resolve $ref in OpenAPI 3.1 schema fields — loader handles refs in prefixItems, contains, patternProperties, etc.
fix: recurse into OpenAPI 3.1 fields in transformOpenAPIToJSONSchema — transform handles all nested schemas
fix: validate sub-schemas in OpenAPI 3.1 schema fields — Schema.validate() recurses into new fields
feat: add const keyword validation to built-in validator — const enforcement without EnableJSONSchema2020()
fix: improve OpenAPI 3.1 spec compliance — paths optional in 3.1, mutualTLS, license url/identifier exclusivity, auto-enable JSON Schema 2020-12 in openapi3filter
feat: add remaining JSON Schema 2020-12 keywords — $id, $anchor, $dynamicRef, $dynamicAnchor, contentMediaType, contentEncoding, contentSchema, discriminator for anyOf
style: fix go fmt formatting
fix: resolve 8 correctness issues — IsEmpty(), JSONLookup(), validate() array items, transform bugs, MarshalYAML, const comparison, webhooks ordering
fix: resolve 8 additional issues — $comment keyword, PrefixItems type consistency, exclusiveBoundToBool data loss, auto-enable 3.1 validation, test coverage gaps, README breaking changes
feat: add $schema, $defs keywords and fix remaining issues — per-schema dialect, local schema definitions, jsonSchemaDialect URI validation, discriminator refactor
fix: support boolean form for unevaluatedProperties and unevaluatedItems — introduce BoolSchema type (with AdditionalProperties kept as alias), handle unevaluatedProperties: false and unevaluatedItems: false (fixes [3.1] Failed to unmarshal unevaluatedProperties: false (boolean form) oasdiff/oasdiff#844)

Open issues for complete 3.1 support

The following items are known gaps that can be addressed in follow-up PRs:

Missing features

~~$schema keyword~~ — Added per-schema dialect declaration.
~~$defs keyword~~ — Added with full support (struct, marshal, unmarshal, IsEmpty, JSONLookup, validate, loader, transform).
~~$comment keyword~~ — Added as first-class field.
$dynamicRef / $dynamicAnchor not resolved — Parsed and serialized but the loader does not resolve them. Schemas using $dynamicRef for recursive references will not work.
Built-in validator ignores most 3.1 keywords — Only validates const. Other 3.1 keywords are silently ignored without EnableJSONSchema2020().
contentMediaType / contentEncoding not validated at runtime — Spec-compliant (annotation-only in 2020-12), but some users may expect validation.
Missing pathItems in Components struct — OAS 3.1 added components/pathItems. Completely absent — silently dropped during parsing.

Bugs / correctness

Breaking API changes

~~ExclusiveMin/ExclusiveMax type changed~~ — Documented in README.
~~PrefixItems type changed~~ — Documented in README.
~~UnevaluatedItems/UnevaluatedProperties type changed from *SchemaRef to BoolSchema~~ — AdditionalProperties kept as type alias for backward compatibility.

Code quality

~~PrefixItems type inconsistency~~ — Changed to SchemaRefs.
~~Discriminator logic duplicated for anyOf~~ — Refactored into resolveDiscriminatorRef helper.

Test coverage

~~No ref resolution test for ContentSchema~~ — Added.
~~No ref resolution test for If/Then/Else~~ — Added.
~~No transformOpenAPIToJSONSchema test for ContentSchema~~ — Added.
~~No Schema.validate() test for ContentSchema~~ — Added.

Test plan

Supersedes

Closes #1102, closes #1114, closes #1118, closes #1119, closes #1120, closes #1121, closes #1122, closes #1123, closes #1124

🤖 Generated with Claude Code

Co-Authored-By: Chance Kirsch <>
Co-Authored-By: RobbertDM <>

Open issues are tracked in the PR getkin#1125 description instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

reuvenharrison · 2026-02-10T10:16:29Z

Open Issues Status Update

22 of 30 issues resolved across commits 9–11.

Resolved issues (22)

Bugs / correctness (11 fixed)

✅ Schema.JSONLookup() — all 23 missing JSON Schema 2020-12 fields added
✅ IsEmpty() — missing checks for PrefixItems, Contains, MinContains, MaxContains, PatternProperties, DependentSchemas, PropertyNames, UnevaluatedItems, UnevaluatedProperties, Examples
✅ validate() array items — relaxed when jsonSchema2020ValidationEnabled or prefixItems present
✅ transformOpenAPIToJSONSchema exclusiveMinimum:false — boolean false now cleaned up
✅ transformOpenAPIToJSONSchema nullable without type — now sets type: ["null"]
✅ MarshalYAML paths:null — only emits paths when non-nil
✅ visitConstOperation json.Number — uses reflect.DeepEqual
✅ Webhooks validation ordering — uses componentNames() for deterministic iteration
✅ exclusiveBoundToBool data loss — numeric bound value preserved in OAS 2.0 conversion
✅ doc.Validate() auto-enable 3.1 — auto-enables EnableJSONSchema2020Validation() for 3.1 docs
✅ jsonSchemaDialect URI validation — now requires a scheme

Missing features (3 added)

✅ $schema keyword — per-schema dialect declaration
✅ $comment keyword — first-class field for round-trip fidelity
✅ $defs keyword — local reusable schema definitions with full ref resolution

Code quality (2 fixed)

✅ PrefixItems type — changed from []*SchemaRef to SchemaRefs
✅ Discriminator duplication — refactored into resolveDiscriminatorRef helper

Breaking API changes (2 documented)

✅ ExclusiveMin/ExclusiveMax type change — documented in README v0.132.0
✅ PrefixItems type change — documented in README v0.132.0

Test coverage (4 added)

✅ Ref resolution test for ContentSchema
✅ Ref resolution test for If/Then/Else
✅ transformOpenAPIToJSONSchema test for ContentSchema
✅ Schema.validate() test for ContentSchema

Remaining open issues (8)

These are larger-scope items for follow-up PRs:

#	Issue	Category
1	`$dynamicRef`/`$dynamicAnchor` not resolved by loader	Missing feature
2	Built-in validator ignores most 3.1 keywords (needs `EnableJSONSchema2020()`)	Missing feature
3	`pathItems` missing from Components struct	Missing feature
4	Built-in validator applies `items` to ALL elements, ignoring `prefixItems`	Bug
5	`patternProperties` omission changes `additionalProperties` semantics	Bug
6	Silent fallback in `visitJSONWithJSONSchema` when compilation fails	Bug
7	`Const: nil` cannot express "value must be null"	Bug
8	`contentMediaType`/`contentEncoding` not validated at runtime (spec-compliant)	Missing feature

reuvenharrison · 2026-02-10T18:21:05Z

Coverage vs Pierre Fenoll's Task List

Assessment of this PR against the tasks outlined by Pierre for complete OpenAPI 3.1 support:

Task	Status	Notes
De/serialization	Complete	All 3.1 fields with full round-trip (marshal/unmarshal/JSONLookup/IsEmpty)
Document validation	Complete	All fields validated, auto-detect 3.1, $ref resolution in loader
JSON Schema validation	Mostly complete	External lib (`santhosh-tekuri/jsonschema/v6`) chosen; 3.1 keywords delegated to it. Built-in validator only handles `const`.
3.0 ↔ 3.1 conversion	Minimal	Only `ExclusiveBound` conversion in `openapi2conv`. No general downgrade/upgrade path.
openapi3gen (reflection)	Not started	Zero changes to `openapi3gen/`
openapi3filter (middleware)	Minimal	Auto-enables JSON Schema 2020-12 mode for 3.1 specs in `ValidateParameter`, `ValidateRequestBody`, `ValidateResponse`
3.0/3.1 coexistence	Complete	`IsOpenAPI3_0()`/`IsOpenAPI3_1()`, `ExclusiveBound` union type, `omitempty` on all 3.1 fields
Tests	Comprehensive	7 new test files, 2 testdata files

What this PR delivers (~60-70% of the full task list)

Full data model for all JSON Schema 2020-12 keywords (26+ new Schema fields)
Document-level features (Webhooks, JSONSchemaDialect, Info.Summary, License.Identifier, mutualTLS)
External JSON Schema 2020-12 validator with automatic 3.1 detection
100% backward compatible with OpenAPI 3.0

Remaining items for follow-up PRs

openapi3gen — Reflection-based generation of 3.1 schemas from Go types (largest gap)
3.0 ↔ 3.1 conversion — Downgrade path (prefixItems→items, type arrays→nullable, $defs→definitions) and upgrade path
openapi3filter — Deeper middleware integration beyond auto-enabling 3.1 mode
Built-in validator — Currently only validates const; other 3.1 keywords require EnableJSONSchema2020()
$dynamicRef resolution — Parsed/serialized but loader does not resolve dynamic references
components/pathItems — OAS 3.1 added this field; currently silently dropped during parsing

Pass source file path to yaml3 decoder so origin locations include the file they were parsed from. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Open issues are tracked in the PR getkin#1125 description instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

stavros-k · 2026-04-07T08:27:48Z

Does this branch solve/allow this?

#1114 (comment)

reuvenharrison · 2026-04-07T12:11:15Z

Yes! This is now supported and tested. I just added a commit that:

Parses sibling keywords alongside $ref when loading an OAS 3.1 document
Applies them onto a copy of the resolved schema after $ref resolution

So your spec is now handled correctly:

status:
  deprecated: true   # sibling keyword — valid in OAS 3.1
  $ref: '#/components/schemas/PingStatus'

After loading, statusRef.Value.Deprecated == true and the $ref is still fully resolved.

The fix is gated on the document version (3.1.x) so OAS 3.0 behaviour is unchanged.

See TestOAS31_RefSiblingKeyword in openapi3/loader_31_schema_refs_test.go for the full test.

Add comprehensive OpenAPI 3.1 / JSON Schema 2020-12 support: - Type arrays with null support (e.g., ["string", "null"]) - JSON Schema 2020-12 keywords: const, examples, prefixItems, contains, minContains, maxContains, patternProperties, dependentSchemas, propertyNames, unevaluatedItems, unevaluatedProperties - Conditional keywords: if/then/else, dependentRequired - ExclusiveBound union type for 3.0 (boolean) and 3.1 (numeric) exclusive bounds - Webhooks support with $ref resolution - Version detection helpers: IsOpenAPI3_0(), IsOpenAPI3_1() - Info.Summary and License.Identifier fields - JSON Schema 2020-12 validator via EnableJSONSchema2020() - Document-level validation option: EnableJSONSchema2020Validation() - Allow $ref alongside other keywords in 3.1 schemas - Handle "null" type in schema validation - Auto-detect 3.1 in cmd/validate Co-Authored-By: Chance Kirsch <> Co-Authored-By: RobbertDM <> Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…, etc.) The loader's resolveSchemaRef only resolved $ref in pre-3.1 fields (items, properties, additionalProperties, not, allOf, anyOf, oneOf). References inside the new OpenAPI 3.1 / JSON Schema 2020-12 fields were silently left unresolved, causing nil Value pointers. This adds ref resolution for: prefixItems, contains, patternProperties, dependentSchemas, propertyNames, unevaluatedItems, unevaluatedProperties. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

The OpenAPI-to-JSON-Schema transformation only recursed into pre-3.1 fields (properties, additionalProperties, items, not, oneOf, anyOf, allOf). Nested schemas inside 3.1 fields with OpenAPI 3.0-isms like nullable:true were not converted, causing incorrect validation. This adds recursion into: prefixItems, contains, patternProperties, dependentSchemas, propertyNames, unevaluatedItems, unevaluatedProperties. Also consolidates the properties/patternProperties/dependentSchemas map iteration into a single loop. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Schema.Validate() (used by doc.Validate()) recursively validates sub-schemas in Items, Properties, AdditionalProperties, etc. but did not recurse into the new OpenAPI 3.1 / JSON Schema 2020-12 fields. Invalid sub-schemas nested inside these fields went undetected. This adds validation for: prefixItems, contains, patternProperties, dependentSchemas, propertyNames, unevaluatedItems, unevaluatedProperties. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Make paths optional in 3.1 (required only in 3.0) - Add mutualTLS security scheme type validation - Validate license url/identifier mutual exclusivity - Enable JSON Schema 2020-12 validation in openapi3filter for 3.1 docs Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Add $id, $anchor, $dynamicRef, $dynamicAnchor identity keywords - Add contentMediaType, contentEncoding, contentSchema vocabulary - Add discriminator support for anyOf (was only oneOf) - Validate jsonSchemaDialect as valid URI Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- IsEmpty(): add missing checks for PrefixItems, Contains, MinContains, MaxContains, PatternProperties, DependentSchemas, PropertyNames, UnevaluatedItems, UnevaluatedProperties, Examples - JSONLookup(): add all 23 missing JSON Schema 2020-12 field cases - validate(): relax items requirement for arrays when in 3.1 mode or when prefixItems is present - transformOpenAPIToJSONSchema: clean up exclusiveMinimum/Maximum false, handle nullable:true without type field - MarshalYAML: only emit paths when non-nil (valid in 3.1) - visitConstOperation: use reflect.DeepEqual for json.Number comparison - Webhooks validation: use componentNames() for deterministic ordering Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Rephrase text to not contain literal json struct tag syntax that triggers the json/yaml tag consistency check. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Open issues are tracked in the PR getkin#1125 description instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Add $comment keyword to Schema struct (MarshalYAML, UnmarshalJSON, IsEmpty, JSONLookup) - Fix PrefixItems type from []*SchemaRef to SchemaRefs for consistency with OneOf/AnyOf/AllOf and JSON Pointer support - Fix exclusiveBoundToBool data loss: preserve numeric bound value when converting OAS 3.1 exclusive bounds to OAS 2.0 - Auto-enable JSON Schema 2020-12 validation for OpenAPI 3.1 documents in doc.Validate() so library users don't need explicit opt-in - Add ref resolution tests for if/then/else and contentSchema - Add transform test for contentSchema with nullable nested schema - Add validate test for contentSchema with invalid sub-schema - Document breaking API changes in README (ExclusiveBound, PrefixItems) - Regenerate docs Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Add $schema keyword to Schema struct for per-schema dialect declaration - Add $defs keyword (Schemas map) for local reusable schema definitions, with full support: struct, marshal, unmarshal, IsEmpty, JSONLookup, validate (recurse), loader (resolve refs), transform (recurse) - Fix jsonSchemaDialect URI validation to require a scheme - Refactor discriminator resolution into shared helper to eliminate code duplication between oneOf and anyOf paths - Regenerate docs Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

OpenAPI 3.1 adds Const (any) and Examples ([]any) fields to Schema. Like Enum/Default/Example, these can contain arbitrary JSON/YAML values that pick up __origin__ metadata from the YAML loader. Strip it on unmarshal to prevent false diffs and unexpected metadata in parsed values. Adds TestOrigin_ConstAndExamplesStripped regression test. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

The origin-tracking YAML loader injects __origin__ as a key inside any map-valued field to record source location. However, typed Go maps (map[string]*Encoding, map[string]*ServerVariable, map[string]*PathItem) treat __origin__ as a real entry, causing false positive diffs when the same spec is loaded from two different file paths. Fix by deleting originKey from these three maps after JSON unmarshaling, mirroring the existing pattern used for Extensions and the unmarshalStringMapP helper already used by Content, Schemas, Headers, etc. Affected: - MediaType.Encoding (map[string]*Encoding) - Server.Variables (map[string]*ServerVariable) - T.Webhooks (map[string]*PathItem) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

In OpenAPI 3.0 / JSON Schema draft-07, $ref replaces its entire object so sibling keywords are silently ignored. In OpenAPI 3.1 / JSON Schema 2020-12, $ref and sibling keywords are both applied. Changes: - SchemaRef gains a `sibling *Schema` field (generated via refs.tmpl) - UnmarshalJSON populates sibling when non-extension fields appear alongside $ref - resolveSchemaRef applies sibling fields onto a copy of the resolved schema, but only for OAS 3.1+ documents (preserves 3.0 behaviour) - applySiblingSchemaFields overlays known annotation/metadata fields (deprecated, description, title, readOnly, writeOnly, example, externalDocs, default) using the extra[] field list so only explicitly present siblings are applied Test: TestOAS31_RefSiblingKeyword in loader_31_schema_refs_test.go loads a 3.1 spec where status has deprecated:true as a $ref sibling and asserts that the resolved Value carries Deprecated==true. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

refs.go header changed from "Code generated by go generate; DO NOT EDIT." to "Code generated by go generate using refs.tmpl; DO NOT EDIT refs.go." Update the committed go doc snapshot to match. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

reuvenharrison · 2026-04-11T15:11:21Z

Note for reviewers

This PR has been rebased onto current master (up to 8fac088), resolving all merge conflicts. All tests pass on the rebased branch.

Conflicts resolved during rebase:

openapi2conv/openapi2_conv.go — upstream's compareParameters (refactor: Replace sort usage with slices package #1147) and our boolPtr/exclusiveBoundToBool were both appended to the file; kept both.
openapi3/refs.go + refs.tmpl — upstream's sort.Strings → slices.Sort refactor (refactor: Replace sort usage with slices package #1147) conflicted with our sibling-keyword parsing block; adopted slices.Sort and preserved the sibling logic.

Review guidance:

The first commit (88393e7 feat: add OpenAPI 3.1 support) is the bulk of the change — 25 files, ~3k lines. The remaining 16 commits are incremental fixes and improvements on top.
The 8 known remaining gaps are documented in the PR description. None are regressions; they are features not yet implemented. They can be tracked as follow-up issues.
The new external dependency (santhosh-tekuri/jsonschema/v6) powers the JSON Schema 2020-12 validator. It is well-maintained (7k+ stars, active releases) and only loaded when EnableJSONSchema2020() is explicitly opted into.
100% backward compatible with existing OpenAPI 3.0 usage — all existing tests pass unmodified.

JSON Schema 2020-12 allows unevaluatedProperties and unevaluatedItems to be either a boolean or a schema object (e.g. `unevaluatedProperties: false`). The fields were typed as *SchemaRef, which caused an unmarshal error when encountering the boolean form. Introduce BoolSchema, a type that handles both boolean and schema forms (same pattern as AdditionalProperties), and use it for all three fields. AdditionalProperties becomes a type alias for BoolSchema so existing code continues to compile unchanged. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

reuvenharrison marked this pull request as draft February 9, 2026 10:01

reuvenharrison mentioned this pull request Feb 9, 2026

feat: add OpenAPI 3.1 support oasdiff/oasdiff#791

Open

5 tasks

reuvenharrison added a commit to oasdiff/kin-openapi that referenced this pull request Feb 10, 2026

chore: remove OPEN_ISSUES.md from repo

0ac50aa

Open issues are tracked in the PR getkin#1125 description instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

reuvenharrison marked this pull request as ready for review February 10, 2026 19:36

reuvenharrison mentioned this pull request Feb 10, 2026

Checker: Add OpenAPI 3.1 breaking change rules oasdiff/oasdiff#793

Open

reuvenharrison referenced this pull request in oasdiff/yaml Mar 13, 2026

feat: add file parameter to UnmarshalWithOrigin

4f1c3d0

Pass source file path to yaml3 decoder so origin locations include the file they were parsed from. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

reuvenharrison added a commit to oasdiff/kin-openapi that referenced this pull request Mar 15, 2026

chore: remove OPEN_ISSUES.md from repo

fa9d195

Open issues are tracked in the PR getkin#1125 description instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

reuvenharrison force-pushed the feat/openapi-3.1-support branch from da004e9 to 4e8f560 Compare March 15, 2026 17:32

AlinsRan pushed a commit to AlinsRan/kin-openapi that referenced this pull request Mar 25, 2026

chore: remove OPEN_ISSUES.md from repo

6a54da4

Open issues are tracked in the PR getkin#1125 description instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

This was referenced Mar 25, 2026

Implementation Plan: Complete OpenAPI 3.1 Support AlinsRan/kin-openapi#1

Closed

Scoped Implementation Plan: OpenAPI 3.1 for CGo Validation Library AlinsRan/kin-openapi#2

Closed

AlinsRan pushed a commit to AlinsRan/kin-openapi that referenced this pull request Mar 26, 2026

chore: remove OPEN_ISSUES.md from repo

228d056

Open issues are tracked in the PR getkin#1125 description instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

This was referenced Mar 26, 2026

feat: OpenAPI 3.1 support with scoped validation enhancements api7/kin-openapi#1

Merged

Feat/openapi 3.1 support AlinsRan/kin-openapi#3

Open

reuvenharrison added a commit to oasdiff/kin-openapi that referenced this pull request Apr 6, 2026

chore: remove OPEN_ISSUES.md from repo

b02c784

Open issues are tracked in the PR getkin#1125 description instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

reuvenharrison force-pushed the feat/openapi-3.1-support branch from e308c1f to 76c0438 Compare April 6, 2026 15:04

reuvenharrison added a commit to oasdiff/kin-openapi that referenced this pull request Apr 6, 2026

chore: remove OPEN_ISSUES.md from repo

8661d2d

Open issues are tracked in the PR getkin#1125 description instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

reuvenharrison and others added 2 commits April 11, 2026 18:07

reuvenharrison and others added 15 commits April 11, 2026 18:07

feat: add const keyword validation to built-in validator

fb21a48

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

style: fix go fmt formatting

6e32b85

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

fix: avoid CI lint match in OPEN_ISSUES.md

38b7418

Rephrase text to not contain literal json struct tag syntax that triggers the json/yaml tag consistency check. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

chore: remove OPEN_ISSUES.md from repo

4c0f804

Open issues are tracked in the PR getkin#1125 description instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

reuvenharrison force-pushed the feat/openapi-3.1-support branch from a280a48 to cdd3f1b Compare April 11, 2026 15:09

reuvenharrison and others added 2 commits April 14, 2026 11:09

docs: regenerate openapi3.txt after BoolSchema type change

36244be

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

This was referenced Apr 14, 2026

[3.1] Failed to unmarshal unevaluatedProperties: false (boolean form) oasdiff/oasdiff#844

Open

OpenAPI 3.1 support? oasdiff/oasdiff#52

Open

reuvenharrison force-pushed the feat/openapi-3.1-support branch 2 times, most recently from e89dd3f to da7268d Compare April 16, 2026 05:55

chore: bump yaml3 to v0.0.12 for unconditional field origin tracking

2532417

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

reuvenharrison force-pushed the feat/openapi-3.1-support branch from da7268d to 2532417 Compare April 16, 2026 09:10

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: add OpenAPI 3.1 support#1125

feat: add OpenAPI 3.1 support#1125
reuvenharrison wants to merge 20 commits intogetkin:masterfrom
oasdiff:feat/openapi-3.1-support

reuvenharrison commented Feb 9, 2026 •

edited

Loading

Uh oh!

reuvenharrison commented Feb 10, 2026

Uh oh!

reuvenharrison commented Feb 10, 2026

Uh oh!

stavros-k commented Apr 7, 2026

Uh oh!

reuvenharrison commented Apr 7, 2026

Uh oh!

reuvenharrison commented Apr 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

reuvenharrison commented Feb 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Core features

Validation

Backward compatibility

Commit history

Open issues for complete 3.1 support

Missing features

Bugs / correctness

Breaking API changes

Code quality

Test coverage

Test plan

Supersedes

Uh oh!

reuvenharrison commented Feb 10, 2026

Open Issues Status Update

Resolved issues (22)

Bugs / correctness (11 fixed)

Missing features (3 added)

Code quality (2 fixed)

Breaking API changes (2 documented)

Test coverage (4 added)

Remaining open issues (8)

Uh oh!

reuvenharrison commented Feb 10, 2026

Coverage vs Pierre Fenoll's Task List

What this PR delivers (~60-70% of the full task list)

Remaining items for follow-up PRs

Uh oh!

stavros-k commented Apr 7, 2026

Uh oh!

reuvenharrison commented Apr 7, 2026

Uh oh!

reuvenharrison commented Apr 11, 2026

Note for reviewers

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

reuvenharrison commented Feb 9, 2026 •

edited

Loading