Update Core V3 API to support RFC7807 formatted errors (problems) #170
Annotations
21 warnings
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
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-media-example "value" property must have required property "title"
|
|
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 "example" property must have required property "title"
|
|
common/src/main/resources/META-INF/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-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 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 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 "content" property must have required property "contentType"
|
|
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"
|
|
app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
rhoas-response-media-type application/json is the only acceptable content type
|
The logs for this run have expired and are no longer available.
Loading