build: add Gradle dependency locking - #81
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Can you please re-create this change against the |
4a2a429 to
f537017
Compare
|
@BenjaminAmos done - rebased onto preview/v4.x-SNAPSHOT, base retargeted, lockfiles regenerated for that branch's module set (single nui-gestalt, gestalt 8.0.0-SNAPSHOT). |
Adds Gradle dependency locking only — deliberately no versioning changes (no nebula.release,
-SNAPSHOTscheme untouched). That's a separate, follow-up concern.dependencyLocking { lockAllConfigurations() }on every subproject, each with its owngradle.lockfile. No buildscript-classpath lockfile needed here — root has nobuildscript {}block.-PnoLockescape hatch used elsewhere in the org: passing it skipsdependencyLocking{}entirely for that build, letting every range resolve fresh — useful for trying an update locally before committing to it via--write-locks.Caveat worth flagging: with dependencies still pinned to literal
-SNAPSHOTcoordinates, locking freezes the version string, not necessarily the underlying artifact bytes — Gradle still treats a-SNAPSHOTcoordinate as a changing module. Full reproducibility follows once versions move offSNAPSHOT.Test plan:
./gradlew build -x testsucceeds with locking active (JDK 21 — the 8.2.1 wrapper here can't run on JDK 26)./gradlew dependencies --write-locksper subproject