actions
actions copied to clipboard
gradle
Action dependency-submission fails after upgrade to Gradle 8.14
After an upgrade to Gradle 8.14, the dependency-submission action has started failing for us.
The commit that upgraded gradle was pushed on the 7th of May 2025, at 11:49 UTC.
Here is our workflow definition:
name: Kotlin dependency graph
on:
workflow_dispatch:
push:
branches: [main]
jobs:
kotlin_dependency_submission:
name: Kotlin dependency graph
permissions:
contents: write # NB: This must be set in the calling workflow as permissions can only be downgraded here.
runs-on: ubuntu-latest
steps:
- name: Checkout sources
uses: actions/checkout@v4
- name: Setup Java
uses: actions/setup-java@v4
with:
distribution: 'temurin'
java-version: 17
- name: Generate and submit dependency graph
uses: gradle/actions/dependency-submission@v4
env:
ORG_GRADLE_PROJECT_GITHUB_USER: ${{ github.actor }}
ORG_GRADLE_PROJECT_GITHUB_TOKEN: ${{ secrets.REDACTED }}
Here is the output from the action:
Run gradle/actions/dependency-submission@v4
Merged default JDK locations into /home/runner/.m2/toolchains.xml
Preparing cache for cleanup.
Restore Gradle state from cache
Enabling dependency graph generation
/home/runner/work/redacted/redacted/gradlew -Dorg.gradle.configureondemand=false -Dorg.gradle.dependency.verification=off -Dorg.gradle.unsafe.isolated-projects=false :ForceDependencyResolutionPlugin_resolveAllDependencies
Starting a Gradle Daemon (subsequent builds will be faster)
Calculating task graph as no cached configuration is available for tasks: :ForceDependencyResolutionPlugin_resolveAllDependencies
Generating dependency graph into '/home/runner/work/lovisa_core/lovisa_core/dependency-graph-reports/kotlin_dependency_graph-kotlin_dependency_submission.json'
Resolving dependency graph plugin 1.4.0 from plugin repository: https://plugins.gradle.org/m2
Resolving dependency graph plugin 1.4.0 from plugin repository: https://plugins.gradle.org/m2
> Task :buildSrc:checkKotlinGradlePluginConfigurationErrors SKIPPED
> Task :buildSrc:generateExternalPluginSpecBuilders FROM-CACHE
> Task :buildSrc:extractPrecompiledScriptPluginPlugins FROM-CACHE
> Task :buildSrc:compilePluginsBlocks FROM-CACHE
> Task :buildSrc:generatePrecompiledScriptPluginAccessors FROM-CACHE
> Task :buildSrc:generateScriptPluginAdapters FROM-CACHE
> Task :buildSrc:compileKotlin FROM-CACHE
> Task :buildSrc:compileJava NO-SOURCE
> Task :buildSrc:compileGroovy NO-SOURCE
> Task :buildSrc:pluginDescriptors
> Task :buildSrc:processResources
> Task :buildSrc:classes
> Task :buildSrc:jar
> Configure project :redacted
Constructing renderer: org.gradle.github.dependencygraph.GitHubDependencyGraphRenderer
GitHubDependencyGraphRenderer: Wrote dependency snapshot to
/home/runner/work/redacted/redacted/dependency-graph-reports/kotlin_dependency_graph-kotlin_dependency_submission.json
gradle/actions: Writing build results to /home/runner/work/_temp/.gradle-actions/build-results/__gradle_actions-1747738242939.json
[Incubating] Problems report is available at: file:///home/runner/work/redacted/redacted/build/reports/problems/problems-report.html
FAILURE: Build failed with an exception.
* What went wrong:
Cannot add task 'ForceDependencyResolutionPlugin_resolveProjectDependencies' as a task with that name already exists.
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.14/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
9 actionable tasks: 3 executed, 6 from cache
BUILD FAILED in 1m 19s
Configuration cache entry stored.
Error: Gradle build failed: see console output for details
Found dependency graph files: /home/runner/work/redacted/redacted/dependency-graph-reports/kotlin_dependency_graph-kotlin_dependency_submission.json
Notice: Submitted dependency-graph-reports/kotlin_dependency_graph-kotlin_dependency_submission.json: Dependency results for the repo have been successfully updated.
Uploading dependency graph file: dependency-graph-reports/kotlin_dependency_graph-kotlin_dependency_submission.json
Artifact name is valid!
Root directory input is valid!
Beginning upload of artifact content to blob storage
Uploaded bytes 27389
Finished uploading artifact content to blob storage!
SHA256 digest of uploaded artifact zip is b5c22388ee6691dbb1610b581cb4650d65e3a1d77a1f5baf8014bf26e688c925
Finalizing artifact upload
Artifact dependency-graph_kotlin_dependency_graph-kotlin_dependency_submission.json.zip successfully finalized. Artifact ID redacted
Does anyone know what might be the cause?
Updated original post with the time of when it started failing. It was on the 7th of May, well before v1.4.0 was taken in use by the action. Please note that the posted output of the workflow run is newer though, and does refer to v1.4.0 of the plugin. But older workflow runs also fail, and they used plugin version 1.3.2.