Skip to content

Make metavariables used in execution spec more consistent #67

Make metavariables used in execution spec more consistent

Make metavariables used in execution spec more consistent #67

Triggered via pull request July 19, 2023 22:13
Status Failure
Total duration 2m 17s
Artifacts 2
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

ci-spec.yml

on: pull_request
build-core-spec
2m 7s
build-core-spec
build-js-api-spec
18s
build-js-api-spec
build-web-api-spec
20s
build-web-api-spec
publish-spec
0s
publish-spec
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
build-core-spec
Process completed with exit code 2.
build-js-api-spec
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-web-api-spec
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-core-spec
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Artifacts

Produced during runtime
Name Size
js-api-rendered Expired
423 KB
web-api-rendered Expired
95 KB