Skip to content

fix: Fixes for error handling when individual pages did not parse #508

fix: Fixes for error handling when individual pages did not parse

fix: Fixes for error handling when individual pages did not parse #508

Triggered via pull request October 17, 2024 17:22
Status Success
Total duration 39m 11s
Artifacts

ci.yml

on: pull_request
build-docs  /  run-docs
30s
build-docs / run-docs
Matrix: code-checks / run-checks
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
build-docs / run-docs
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
build-docs / run-docs
Cache paths are empty. Please check the previous logs and make sure that the python version is specified
code-checks / run-checks (3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
code-checks / run-checks (3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
code-checks / run-checks (3.12)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/