Skip to content

Gradle lockfile is not updated for single-module root project using standard version catalog #14788

Description

@adunning

Is there an existing issue for this?

  • I have searched the existing issues

Package ecosystem

Gradle

Package manager version

Gradle 9.4.1 (via the Gradle wrapper)

Language version

Java 25

Manifest location and content before the Dependabot update

Repository: https://github.com/adunning/xml-model-validator

Relevant files:

This is a single-module root project.

It uses a standard Gradle version catalog in /gradle/libs.versions.toml and enables dependency locking in /build.gradle.kts:

dependencyLocking {
    lockAllConfigurations()
}

dependabot.yml content

https://github.com/adunning/xml-model-validator/blob/40de5b3d7759a2b79534dca0a799304788d5abd3/.github/dependabot.yml

Updated dependency

name.dmaus.schxslt:schxslt2 from 1.10.1 to 1.10.3

What you expected to see, versus what you actually saw

I expected Dependabot to update both:

  • gradle/libs.versions.toml
  • gradle.lockfile

Instead, it updated only gradle/libs.versions.toml and left gradle.lockfile stale.

Native package manager behavior

After making the same version change locally and running:

./gradlew dependencies --write-locks

Gradle updates gradle.lockfile correctly, as shown in adunning/xml-model-validator@40de5b3.

Images of the diff or a link to the PR, issue, or logs

Dependabot PR showing the stale result:
adunning/xml-model-validator#5

Related issue:
#14633

Smallest manifest that reproduces the issue

No response

Metadata

Metadata

Labels

Type

No type

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions