Skip to content
CI

Use Future.successful wherever possible #431

Sign in to view logs

Use Future.successful wherever possible

Use Future.successful wherever possible #431

Triggered via pull request November 9, 2024 03:44
@gravetiigravetii
opened #361
gravetii:refactor_futures
Status Success
Total duration 2m 12s
Artifacts –

ci.yml

on: pull_request
build
1m 38s
build
format
1m 57s
format
test
2m 2s
test
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
build
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/
format
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/
test
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/