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
During the creation of the release snapshot for r4.1 (Sync26), two OAS 3.x schema validation errors were detected:
code/API_definitions/device-swap.yaml:483:13 — [S-209] Property "name" is not expected to be here.
code/API_definitions/device-swap.yaml:484:11 — [S-209] Property "in" is not expected to be here.
These errors prevent the snapshot from being finalized and block the release review process. According to CAMARA Release Management policy, OAS validation errors must be fixed on the main branch before snapshot creation can proceed.
Expected behavior
The OpenAPI 3.x schema validation should pass without errors. The properties "name" and "in" at lines 483-484 should either be removed or relocated to their correct position within the OpenAPI schema structure (typically within a parameters array or appropriate schema object).
Alternative solution
If these properties are intentional or required by the API specification, they should be documented with:
A clear explanation of why they are needed
A reference to the OpenAPI 3.x specification section that permits their usage
A fix to the schema validation rules if this is a valid use case not currently covered by the linter
Additional context
This issue blocks the release snapshot r4.1-a2b06c8
Problem description
During the creation of the release snapshot for r4.1 (Sync26), two OAS 3.x schema validation errors were detected:
code/API_definitions/device-swap.yaml:483:13— [S-209] Property "name" is not expected to be here.code/API_definitions/device-swap.yaml:484:11— [S-209] Property "in" is not expected to be here.These errors prevent the snapshot from being finalized and block the release review process. According to CAMARA Release Management policy, OAS validation errors must be fixed on the
mainbranch before snapshot creation can proceed.Expected behavior
The OpenAPI 3.x schema validation should pass without errors. The properties "name" and "in" at lines 483-484 should either be removed or relocated to their correct position within the OpenAPI schema structure (typically within a
parametersarray or appropriate schema object).Alternative solution
If these properties are intentional or required by the API specification, they should be documented with:
Additional context
mainCC: @camaraproject/device-swap_codeowners