bump: oasdiff v1.23.0 #289
reuvenharrisontest-breaking.yaml
on: pull_request
Test breaking changes
8s
Test fail on breaking changes
9s
Test breaking action with petsotre to validate no error of unable to process file command 'output...
10s
Test breaking action with composed option
10s
Test breaking changes with deprecation
10s
Test breaking action with flatten-allof option
7s
Test breaking action with err-ignore option
13s
Test breaking action picks up fail-on from .oasdiff.yaml
10s
Test breaking action picks up err-ignore from .oasdiff.yaml
11s
Annotations
11 errors, 5 warnings, and 7 notices
|
response-property-became-optional:
specs/revision-allof.yaml#L0
in API GET /pets/{petId} the response property `name` became optional for the status `200`
|
|
api-removed-without-deprecation:
specs/base.yaml#L0
in API GET /pets api removed without deprecation
|
|
api-removed-without-deprecation:
specs/glob/base/base.yaml#L0
in API GET /pets api removed without deprecation
|
|
response-property-became-optional:
specs/petstore-revision.yaml#L0
in API GET /pets/{petId} the response property `name` became optional for the status `200`
|
|
response-property-became-optional:
specs/petstore-revision.yaml#L0
in API GET /pets/{petId} the response property `message` became optional for the status `default`
|
|
response-property-became-optional:
specs/petstore-revision.yaml#L0
in API POST /pets the response property `message` became optional for the status `default`
|
|
new-required-request-property:
specs/petstore-revision.yaml#L102
in API POST /pets added the new required request property `tag2`
|
|
response-property-became-optional:
specs/petstore-revision.yaml#L0
in API GET /pets the response property `message` became optional for the status `default`
|
|
response-property-became-optional:
specs/petstore-revision.yaml#L0
in API GET /pets the response property `items/name` became optional for the status `200`
|
|
api-stability-decreased:
specs/base-deprecation.yaml#L15
in API GET /pets endpoint stability level decreased from `stable` to `beta`
|
|
api-removed-without-deprecation:
specs/base.yaml#L0
in API GET /pets api removed without deprecation
|
|
response-optional-property-removed:
specs/revision-breaking-warn.yaml#L0
in API GET /pets/{petId} removed the optional property `tag` from the response with the `200` status
|
|
response-optional-property-removed:
specs/revision-breaking-warn.yaml#L0
in API GET /pets removed the optional property `items/tag` from the response with the `200` status
|
|
response-optional-property-removed:
specs/petstore-revision.yaml#L0
in API GET /pets/{petId} removed the optional property `tag` from the response with the `200` status
|
|
request-property-removed:
specs/petstore-revision.yaml#L0
in API POST /pets removed the request property `tag`
|
|
response-optional-property-removed:
specs/petstore-revision.yaml#L0
in API GET /pets removed the optional property `items/tag` from the response with the `200` status
|
|
Test breaking action with flatten-allof option
oasdiff: couldn't post the review link as a PR comment (HTTP 403). On fork pull requests the token is read-only; otherwise grant 'permissions: pull-requests: write'. The link is still in the job summary.
|
|
Test breaking changes
oasdiff: couldn't post the review link as a PR comment (HTTP 403). On fork pull requests the token is read-only; otherwise grant 'permissions: pull-requests: write'. The link is still in the job summary.
|
|
Test fail on breaking changes
oasdiff: couldn't post the review link as a PR comment (HTTP 403). On fork pull requests the token is read-only; otherwise grant 'permissions: pull-requests: write'. The link is still in the job summary.
|
|
Test breaking action with composed option
oasdiff: the side-by-side review isn't available in composed mode (-c). The breaking-change report above is unaffected.
|
|
Test breaking action with petsotre to validate no error of unable to process file command 'output...
oasdiff: couldn't post the review link as a PR comment (HTTP 403). On fork pull requests the token is read-only; otherwise grant 'permissions: pull-requests: write'. The link is still in the job summary.
|
|
Test breaking changes with deprecation
oasdiff: couldn't post the review link as a PR comment (HTTP 403). On fork pull requests the token is read-only; otherwise grant 'permissions: pull-requests: write'. The link is still in the job summary.
|
|
Test breaking action picks up fail-on from .oasdiff.yaml
oasdiff: couldn't post the review link as a PR comment (HTTP 403). On fork pull requests the token is read-only; otherwise grant 'permissions: pull-requests: write'. The link is still in the job summary.
|