Skip to content

feat: update limits for outgoing payment access #349

feat: update limits for outgoing payment access

feat: update limits for outgoing payment access #349

Triggered via pull request August 23, 2024 04:27
Status Failure
Total duration 28s
Artifacts

validate-openapi.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 2 warnings
validate: openapi/auth-server.yaml#L107
oas3-valid-media-example "0" property must match exactly one schema in oneOf
validate: openapi/auth-server.yaml#L112
oas3-valid-media-example "limits" property must match exactly one schema in oneOf
validate: openapi/auth-server.yaml#L175
oas3-valid-media-example "0" property must match exactly one schema in oneOf
validate: openapi/auth-server.yaml#L180
oas3-valid-media-example "limits" property must match exactly one schema in oneOf
validate: openapi/auth-server.yaml#L268
oas3-valid-media-example "0" property must match exactly one schema in oneOf
validate: openapi/auth-server.yaml#L273
oas3-valid-media-example "limits" property must match exactly one schema in oneOf
validate
Process completed with exit code 1.
validate
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
validate
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/