Develocity - Publish Maven Build Scans #28536
Triggered via workflow run
May 28, 2026 19:03
dependabot[bot]
completed
8750950
Status
Success
Total duration
24m 7s
Artifacts
–
develocity-publish-build-scans.yml
on: workflow_run
publish-build-scans
15s
Annotations
3 warnings and 1 notice
|
publish-build-scans
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@v4, gradle/develocity-actions/maven-publish-build-scan@974e8dbcbda40db6828fc35f349c80a7c0e71529, gradle/develocity-actions/setup-maven@974e8dbcbda40db6828fc35f349c80a7c0e71529. 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/
|
|
publish-build-scans
/home/runner/work/_temp/maven-build-scan-data/build-metadata.json is not readable, ignoring
|
|
publish-build-scans
No files were found with the provided path: /home/runner/work/_temp/maven-build-scan-data/build-metadata.json. No artifacts will be uploaded.
|
|
publish-build-scans
Injecting build scans into build report
|