You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an existing workflow that is calling gradle-build-action@v2 and successfully builds and submits the dependency graph for my projects. Today I've tried upgrading that to the new dependency-submission action and couldn't get it to work.
Current action:
- name: Run gradlew task to analyse the runtime dependencies
uses: gradle/gradle-build-action@v2
env:
DEPENDENCY_GRAPH_INCLUDE_CONFIGURATIONS: runtimeClasspath
with:
gradle-version: "5.6"
dependency-graph: generate-and-submit
build-root-directory: .
arguments: dependencies
New version which fails:
- name: Run gradlew task to analyse the runtime dependencies
uses: gradle/actions/dependency-submission@v3
env:
DEPENDENCY_GRAPH_INCLUDE_CONFIGURATIONS: runtimeClasspath
with:
gradle-version: "5.6"
dependency-graph: generate-and-submit
build-root-directory: .
The error I'm seeing during the build, like mentioned in the title, is:
(...)
Welcome to Gradle 5.6!
Here are the highlights of this release:
- Incremental Groovy compilation
- Groovy compile avoidance
- Test fixtures for Java projects
- Manage plugin versions via settings script
For more details see https://docs.gradle.org/5.6/release-notes.html
Unknown command-line option '--dependency-verification'.
USAGE: gradle [option...] [task...]
I've not been able to understand when that CLI option has been introduced, but it really does not seem to be there in version 5.6.
The text was updated successfully, but these errors were encountered:
I have an existing workflow that is calling
gradle-build-action@v2
and successfully builds and submits the dependency graph for my projects. Today I've tried upgrading that to the newdependency-submission
action and couldn't get it to work.Current action:
New version which fails:
The error I'm seeing during the build, like mentioned in the title, is:
I've not been able to understand when that CLI option has been introduced, but it really does not seem to be there in version 5.6.
The text was updated successfully, but these errors were encountered: