Skip to content
Java CI with Maven

General rework of release process. Preparing test on branch #7

Sign in to view logs

General rework of release process. Preparing test on branch

General rework of release process. Preparing test on branch #7

Triggered via push October 2, 2024 15:46
@francis-pouatchafrancis-pouatcha
pushed 6484322
fpo-release-cmd
Status Failure
Total duration 37s
Artifacts –

maven-release.yaml

on: push
build
25s
build
release
4s
release
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
release
Process completed with exit code 2.
build
Process completed with exit code 1.
release
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
release
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, 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/
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, 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/