I've lost my mind, for some reason gradle is removing

errorprone

scope from my locks, unlocking the dependency. I can't figure out why it's different (correct) locally only. That's kind of good though, if I have the only environment that produces the correct result... then everyone else can reproduce the incorrect one. I thought I had it figured out, but my automated build still cleans it. This is the last PR where it did it https://github.com/xenoterracide/spring-app-commons/pull/11 and the job that creates those PR's https://github.com/xenoterracide/spring-app-commons/blob/main/.github/workflows/update-java.yml I have verified that errorprone is running in CI (by causing it to fail). No I don't have any init scripts locally, I had vampire test this locally too. I thought I had it. That it was related to using

buildScript { depenendencyLocking.lockAllConfigurations() }

instead of

buildScript { dependencyLocking { lockAllConfigurations() }}

but I guess that wasn't it. That build does produce a build scan https://github.com/xenoterracide/spring-app-commons/actions/runs/8274833680