Skip to content
Call Gradle CI

fix: allow lazy loading of maxViolations (refs #23) #21

Sign in to view logs

fix: allow lazy loading of maxViolations (refs #23)

fix: allow lazy loading of maxViolations (refs #23) #21

Triggered via push November 9, 2024 05:24
@tomasbjerretomasbjerre
pushed 0362591
master
Status Success
Total duration 1m 56s
Artifacts –

gradle-ci.yml

on: push
Matrix: call-workflow / build
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
call-workflow / Java 17 (ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
call-workflow / Java 17 (ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-java@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
call-workflow / Java 21 (ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
call-workflow / Java 21 (ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-java@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/