chore: enable Gradle dependency locking#11
Merged
Conversation
Lock all configurations per Jimdo convention and commit generated lockfiles. Update with: ./gradlew dependencies --write-locks Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
bijancn
marked this pull request as ready for review
July 14, 2026 08:04
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Gradle dependency lockfiles make builds reproducible and improve supply-chain integrity: every resolved dependency version is pinned and reviewed in source control, so silent upstream version drift can no longer change what we ship. This is part of the org-wide lockfile adoption sweep; the convention mirrors Jimdo/business-entity-service and Jimdo/geoip-service.
What changed
build.gradle.kts: enableddependencyLocking { lockAllConfigurations() }at project scope and inside the existingbuildscript {}block.gradle.lockfile: generated lock state for all project configurations.buildscript-gradle.lockfile: generated lock state for the buildscript classpath.No dependency versions were changed.
How it was verified locally
./gradlew --no-daemon dependencies --write-locks— lock state persisted for buildscript and project, no resolution failures../gradlew --no-daemon build— full build green on JDK 21 (Corretto 21), all tests passed (including Testcontainers-based integration tests and the ArchUnit architecture test).Maintainer note
When changing dependencies, regenerate the lockfiles with:
🤖 Generated with Claude Code