Skip to content

Un-nest Java packages from api since they aren't API-specific #259

Un-nest Java packages from api since they aren't API-specific

Un-nest Java packages from api since they aren't API-specific #259

Triggered via push September 27, 2024 21:23
Status Success
Total duration 4m 39s
Artifacts

ci.yaml

on: push
ci-client-verify
9s
ci-client-verify
ci-server-verify
4m 5s
ci-server-verify
ci-complete
4s
ci-complete
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
ci-client-verify
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/setup-java@v3, actions/cache/restore@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci-client-verify
Unexpected input(s) 'clientVersion', valid inputs are ['']
ci-client-verify
Unexpected input(s) 'clientVersion', valid inputs are ['']
ci-server-verify
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/setup-java@v3, actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci-complete
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/