Skip to content

build: Fix relative path in sdk-platform-java-dependency_compatibility_test #401

build: Fix relative path in sdk-platform-java-dependency_compatibility_test

build: Fix relative path in sdk-platform-java-dependency_compatibility_test #401

Re-run triggered March 31, 2026 15:37
Status Success
Total duration 11m 2s
Artifacts

sdk-platform-java-ci.yaml

on: pull_request
build(21) except self-service clients
12m 39s
build(21) except self-service clients
build(25) except self-service clients
12m 42s
build(25) except self-service clients
build(8) except for gapic-generator-java
3m 48s
build(8) except for gapic-generator-java
build(8) for gapic-generator-java
10m 55s
build(8) for gapic-generator-java
build(8) for showcase
9m 21s
build(8) for showcase
showcase-clirr
5m 12s
showcase-clirr
gapic-generator-java-bom
2m 33s
gapic-generator-java-bom
unmanaged_dependency_check
10m 55s
unmanaged_dependency_check
dependency_analyzer_unit_test
1m 23s
dependency_analyzer_unit_test
Matrix: build
Matrix: showcase
Fit to window
Zoom out
Zoom in

Annotations

1 warning
unmanaged_dependency_check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v3, actions/setup-java@v4, stCarolas/setup-maven@v4.5. 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/