build(gradle): Set group so composite substitution works automatically - #1410
Merged
Conversation
runningcode
force-pushed
the
no/renovate-skip-snapshots-runtime
branch
from
August 21, 2026 10:36
eb0cea8 to
f4aa1f9
Compare
runningcode
changed the title
runningcode
force-pushed
the
no/renovate-skip-snapshots-runtime
branch
from
August 21, 2026 11:58
f4aa1f9 to
fc8398a
Compare
Renovate's --write-verification-metadata invocation fails with "The root project is not yet available for build". The cause is the explicit dependencySubstitution block on sentry-snapshots-runtime: declaring substitutions by hand is how you tell Gradle it need not configure an included build to discover its coordinates, so nothing ever configures that build, and WriteDependencyVerificationFile then walks every build in the tree at build-finish and dies on the one with no root project. Those blocks exist because automatic substitution was not matching, and it was not matching because Gradle keys it off project.group:project.name while these builds only declare GROUP, a Vanniktech maven-publish convention that sets the publication coordinates and leaves project.group empty. Set group from GROUP and drop both blocks. The substitution then happens automatically, and discovering it configures the included builds, which is what the verification metadata walk needs. This also removes a footgun: with the blocks gone but no group, anything that started depending on sentry-snapshots-runtime would have silently resolved against a published artifact instead of the local build. Publishing is untouched -- pom-default.xml and module.json are byte-identical for both builds, because Vanniktech was already writing io.sentry into them.
runningcode
force-pushed
the
no/renovate-skip-snapshots-runtime
branch
from
August 21, 2026 12:09
fc8398a to
cdeef57
Compare
runningcode
marked this pull request as ready for review
August 21, 2026 13:06
runningcode
requested review from
0xadam-brown,
adinauer,
markushi and
romtsn
as code owners
August 21, 2026 13:06
0xadam-brown
approved these changes
Aug 21, 2026
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.
For composite builds, dependency substitution works automatically. However because we aren't setting the
groupproperty in gradle, the dependency substituion doesn't work. This sets thegroupin gradle so thatThis sets the
groupon the two projects using dependency substituion works properly.This simplifies the code and should hopefully also fix the build error we are getting in renovate
The root project is not yet available for buildGRADLE-116
#skip-changelog