Successful Jenkins pipeline run does not upload snapshot to Github, outdated dependency graph #120
Description
Myself and fellow developers have noticed that the dependency graphs in our repositories are not updating in Github after successful runs of the maven dependency submission action in the respective Jenkins pipelines.
For example: [repo] shows that the dependency (in the Github dependency graph) for [package] is at 2.0.2-RELEASE, even though it was upgraded in August to be at 2.0.4-RELEASE. It also says that it's a transitive dependency, even though the pom specifies the dependency within it.
The maven-dependency-submission-action, used at version 5.0.0 (also tried with version 4.1.3 and 4.0.3), generates the entire graph, in which the [package] dependency is at 2.0.4-RELEASE, says that the snapshot upload was successful, but the GitHub dependency graph does not show any update, in date of last submission or in version
In Jenkins, within the step, we can see the dependency graph being generated and the updated packages showing, none of that is being translated to Github though.
::notice::Snapshot successfully created at 2025-11-07T16:53:13.358Z completed. is output at the end of the step. Running the maven-dependency-submission-action-win.exe locally on the same commit and repository also yields a successful snapshot created message, but Github does not update.