This appears to happen to all dependencies managed by Gradle. I saw this happening on the following examples:
Bump jakarta.validation:jakarta.validation-api from 3.0.2 to 3.1.0
Bump org.jetbrains.kotlin:kotlin-reflect from 1.9.24 to 2.0.0
The Pull Requests still had the correct title. But the commit message is no longer useful.
What you expected to see, versus what you actually saw
I expect the commit message from Dependabot to be something that in the headline mentions the dependency that's updated, the old version, and the new version. Something like this:
Bump io.cucumber:cucumber-spring from 7.17.0 to 7.18.0
What I actually saw was a commit message that omitted the Bump part of the commit message and therefore was only the following:
This leads to a history that shows only --- as the commit summary, which is not very helpful.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
I have not created an isolated test case yet. I will create one in a public repository, and to see whether it works, I will have to wait for Dependabot to pick it up.
Is there an existing issue for this?
Package ecosystem
Gradle
Package manager version
8.7
Language version
Java 21 / Kotlin
Manifest location and content before the Dependabot update
No response
dependabot.yml content
Updated dependency
This appears to happen to all dependencies managed by Gradle. I saw this happening on the following examples:
The Pull Requests still had the correct title. But the commit message is no longer useful.
What you expected to see, versus what you actually saw
I expect the commit message from Dependabot to be something that in the headline mentions the dependency that's updated, the old version, and the new version. Something like this:
What I actually saw was a commit message that omitted the
Bump
part of the commit message and therefore was only the following:This leads to a history that shows only
---
as the commit summary, which is not very helpful.Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
I have not created an isolated test case yet. I will create one in a public repository, and to see whether it works, I will have to wait for Dependabot to pick it up.