[REST API] Updated the branch API to be a bit more REST compatible #142
Annotations
21 warnings
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
common/src/main/resources/META-INF/openapi.json#L1
oas3-api-servers
|
common/src/main/resources/META-INF/openapi.json#L1
rhoas-servers-config
|
common/src/main/resources/META-INF/openapi.json#L17
oas3-valid-media-example "value" property type must be string
|
common/src/main/resources/META-INF/openapi.json#L17
oas3-valid-schema-example "version" property type must be string
|
common/src/main/resources/META-INF/openapi.json#L17
oas3-valid-schema-example "example" property must match pattern "^[a-zA-Z0-9._\-+]{1,256}$"
|
common/src/main/resources/META-INF/openapi.json#L17
oas3-valid-schema-example "example" property must be equal to one of the allowed values: "OUTBOUND", "INBOUND". Did you mean "INBOUND"?
|
common/src/main/resources/META-INF/openapi.json#L17
oas3-valid-schema-example "content" property must have required property "contentType"
|
common/src/main/resources/META-INF/openapi.json#L17
oas3-valid-schema-example "createdOn" property must match format "date-time"
|
common/src/main/resources/META-INF/openapi.json#L17
oas3-valid-schema-example "example" property must have required property "labels"
|
common/src/main/resources/META-INF/openapi.json#L17
rhoas-response-media-type application/json is the only acceptable content type
|
|
|
app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
oas3-valid-media-example "value" property type must be string
|
app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
oas3-valid-schema-example "version" property type must be string
|
app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
oas3-valid-schema-example "example" property must be equal to one of the allowed values: "OUTBOUND", "INBOUND". Did you mean "INBOUND"?
|
app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
oas3-valid-schema-example "example" property must have required property "group"
|
app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
oas3-valid-schema-example "example" property must match pattern "^[a-zA-Z0-9._\-+]{1,256}$"
|
app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
oas3-valid-schema-example "example" property must have required property "groupId"
|
app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
oas3-valid-schema-example "createdOn" property must match format "date-time"
|
app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
oas3-valid-schema-example "example" property must have required property "labels"
|
The logs for this run have expired and are no longer available.
Loading