Skip to content

Update all dependencies #363

Update all dependencies

Update all dependencies #363

Triggered via pull request April 3, 2026 16:57
Status Failure
Total duration 2m 52s
Artifacts

1.pipeline.yml

on: pull_request
Build + unit tests  /  gradle build test
1m 14s
Build + unit tests / gradle build test
Integration tests  /  gradle intTest
32s
Integration tests / gradle intTest
Code Analysis (multi)  /  ...  /  CodeQL Analysis
1m 31s
Code Analysis (multi) / GitHub CodeQL Analysis / CodeQL Analysis
Code Analysis (multi)  /  ...  /  Trivy scan (JVM)
1m 13s
Code Analysis (multi) / Trivy Security Scan / Trivy scan (JVM)
Publish javadoc (GitHub Pages)  /  Generate Javadoc
Publish javadoc (GitHub Pages) / Generate Javadoc
Create release  /  gradle release
Create release / gradle release
Publish artifact (Maven Central)  /  gradle publish (Maven Central)
Publish artifact (Maven Central) / gradle publish (Maven Central)
Publish javadoc (GitHub Pages)  /  Deploy (GH Pages)
Publish javadoc (GitHub Pages) / Deploy (GH Pages)
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
Integration tests / gradle intTest
Process completed with exit code 1.
Code Analysis (multi) / Trivy Security Scan / Trivy scan (JVM)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Code Analysis (multi) / GitHub CodeQL Analysis / CodeQL Analysis
Starting April 2026, the CodeQL Action will skip computing file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. To opt out of this change, set the `CODEQL_ACTION_FILE_COVERAGE_ON_PRS` environment variable to `true`. Alternatively, create a custom repository property with the name `github-codeql-file-coverage-on-prs` and the type "True/false", then set this property to `true` in the repository's settings.