Skip to content

Adding a requirement - backwards compatibility (not) #270

Adding a requirement - backwards compatibility (not)

Adding a requirement - backwards compatibility (not) #270

Triggered via pull request January 23, 2024 14:49
Status Success
Total duration 2m 56s
Artifacts 1

auto-publish.yml

on: pull_request
Matrix: Build, Validate and Deploy
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Build, Validate and Deploy (explainer/index.html, explainer/index.html)
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/
Build, Validate and Deploy (guidelines/index.html, guidelines/index.html)
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/
Build, Validate and Deploy (requirements/index.html, requirements/index.html)
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/
Build, Validate and Deploy (use-cases/index.html, use-cases/index.html)
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
spec-prod-result Expired
765 KB