Skip to content

chore(deps): update mkdocs-macros-plugin requirement #1995

chore(deps): update mkdocs-macros-plugin requirement

chore(deps): update mkdocs-macros-plugin requirement #1995

Triggered via push October 24, 2024 10:46
Status Success
Total duration 13m 13s
Artifacts

build.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
Build
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
Build
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
Build
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
Build
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
Build
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
Build
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
Build
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
Build
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
Build
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
Build
Unexpected error: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
Build
The following actions use a deprecated Node.js version and will be forced to run on node20: jpribyl/action-docker-layer-caching@v0.1.1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/