Skip to content

Fixed issue causing CLI errors when using --help or --version, while … #13

Fixed issue causing CLI errors when using --help or --version, while …

Fixed issue causing CLI errors when using --help or --version, while … #13

Triggered via push March 15, 2024 03:19
Status Failure
Total duration 1m 22s
Artifacts

build.yml

on: push
Build Java Artifacts
1m 14s
Build Java Artifacts
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
Build Java Artifacts
Process completed with exit code 1.
Build Java Artifacts
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: stCarolas/setup-maven@07fbbe97d97ef44336b7382563d66743297e442f. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build Java Artifacts
Advanced Security must be enabled for this repository to use code scanning.
Build Java Artifacts
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Advanced Security must be enabled for this repository to use code scanning.
Build Java Artifacts
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.16.4.
Build Java Artifacts
Advanced Security must be enabled for this repository to use code scanning.
Build Java Artifacts
Advanced Security must be enabled for this repository to use code scanning.