You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug: no details when securitySchemes.*.name changes #802
When a change is introduced solely to the name property of an apiKey securitySchemes object in an OpenAPI 3.1 specification, openapi‑diff merely reports that a change occurred without providing any line‑level detail (path, field changed, old and new values).In addition, there appears to be no way to disable this rule via the usual options. (incompatible.security.scheme.scheme.change:false)
==========================================================================
== API CHANGE LOG ==
==========================================================================
**** Restful API
--------------------------------------------------------------------------
-- What's Changed --
--------------------------------------------------------------------------
- GET /rest/v1/info
--------------------------------------------------------------------------
-- Result --
--------------------------------------------------------------------------
API changes are backward compatible
--------------------------------------------------------------------------
This isn't specific to OpenAPI 3.1, so I'm removing the 3.1 label. The same apiKey name change behaves identically with openapi: 3.0.1 and 3.1.0 on current master: the operation is marked as changed/incompatible, but there's no detail about which scheme property changed (old → new name).
Note: in the attached old.json, security sits at the path-item level instead of under the operation. The parser ignores it there, which is why that diff came out as "backward compatible".
Activity
DrSatyr commentedon Nov 14, 2026
This isn't specific to OpenAPI 3.1, so I'm removing the 3.1 label. The same apiKey
namechange behaves identically withopenapi: 3.0.1and3.1.0on current master: the operation is marked as changed/incompatible, but there's no detail about which scheme property changed (old → new name).Note: in the attached
old.json,securitysits at the path-item level instead of under the operation. The parser ignores it there, which is why that diff came out as "backward compatible".fix OpenAPITools#802: match security schemes by key first and align s…