Skip to content
Node.js CI

feature: directly link content records (routing) #280

Sign in to view logs

feature: directly link content records (routing)

feature: directly link content records (routing) #280

Triggered via pull request November 4, 2024 13:11
@jurgenbelienjurgenbelien
synchronize #195
feat/link-records
Status Failure
Total duration 37s
Artifacts –

node-ci.yml

on: pull_request
setup
5s
setup
lint-code
13s
lint-code
validate-html
8s
validate-html
unit-test
13s
unit-test
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
validate-html
Process completed with exit code 1.
lint-code
Process completed with exit code 1.
unit-test
Process completed with exit code 1.
setup
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
validate-html
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
lint-code
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
unit-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/