Skip to content
Github CI

[maven-release-plugin] prepare for next development iteration #391

Sign in to view logs

[maven-release-plugin] prepare for next development iteration

[maven-release-plugin] prepare for next development iteration #391

Triggered via push September 29, 2024 15:53
@fpaponfpapon
pushed bf9b1a2
master
Status Success
Total duration 1m 12s
Artifacts –

maven.yml

on: push
Main Build
1m 5s
Main Build
Security Audit
46s
Security Audit
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Security Audit
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v1, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Security Audit
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v1, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Main Build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Main Build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/