A response without a schema breaks generated type definitions
A valid response content entry with examples but no schema caused the generator to emit only an error comment instead of a useful operation type.
This page traces one detailed external-report case through the available source and release evidence. The public-record census includes additional discovery channels and separately identified recurrences.
- Report
- Issue #1618
- Reporter
- dissemond-bitside
- Reported
- April 2, 2026
- Reported version
- 2.4.0
- Matched window
- Included
- First affected release entered matched window
- No
- Origin classification
- Pre-existing before 2026
- Classification confidence
- High
- Chronology confidence
- High
- Accepted correction
- PR #1621
- First fixed release
- 2.5.0
- Report to release
- 1.65 elapsed daysReport: 2026-04-02T02:19:16Z; corrected publication: 2026-04-03T17:57:55.215Z.
Historical test demonstration and reproducible commands
Finding
The unsafe dereference dates to 2022. In the audit’s year-based taxonomy, this old regression is still pre-existing in 2025.
Evidence trail
Origin
Exact origin: cf49cad1, committed October 20, 2022; first affected release 0.13.0. A response-content refactor assumed that every media type supplied a schema and dereferenced the missing value.
Source history and behavioral evidence
Source history identifies the 2022 response-type refactor that introduced the unconditional schema access. The fix falls back to unknown and tests generation from content without a schema.
Release chronology
The faulty implementation appears in 0.13.0; the accepted fix shipped in 2.5.0 one day after the report.