Skip to content
Build

http91 bearer token support #338

Sign in to view logs

http91 bearer token support

http91 bearer token support #338

Triggered via pull request August 16, 2024 09:16
@davidradldavidradl
synchronize #117
davidradl:http91
Status Success
Total duration 2m 53s
Artifacts –

build.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
build (1.17.2)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-java@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (1.17.2)
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
build (1.18.1)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-java@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (1.18.1)
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
build (1.16.3)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-java@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (1.16.3)
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.