Release new version of submodule if dependency changed

[cyberveseli]

Hello
I am running multi-project architecture and we are doing version per module.
Let's say we Have ProjectA and ProjectB. Both projects contain build.gradle.kts with following lines:

plugins {
    id("pl.allegro.tech.build.axion-release") version "1.13.14"
}
scmVersion {
    tag {
        prefix = "$project.name-"
    }
}
project.version = scmVersion.version

ProjectB depends on ProjectA and has one more line:

dependencies {
    implementation(project(":ProjectA"))
}

Once we commit and push changes to ProjectA it's release new version of ProjectA and that's fine.
Problem:
ProjectB depends on ProjectA and we want to release new version of ProjectB if something changed in ProjectA but gradle release print out nothing to release
Are there any solution to this?
Somehow, axion should understand that if dependecy has some changes we should release new version of dependent modules.

I think this is similar to: #262 and #326

[bgalek]

Hi! Unfortunately, I think that to support your setup we would need to recover this PR #326, would you like to participate? :)

[Olatunji-Longe]

I have achieved this by doing something as simple as

build.gradle

def includes = []
rootProject.allprojects.forEach { it ->
    includes.add("${it.projectDir.parentFile.name}/${it.projectDir.name}")
}

scmVersion {
    monorepo {
        include(includes)
    }
}

Ref: Documentation which says;

Use the include configuration parameter within a monorepo block to identify dependencies directories that should be added to consideration when calculating whether to increment the version of the parent project

Note - I have all my modules nested in a subdirectory of my project root, so I've used ${it.projectDir.parentFile.name}/${it.projectDir.name} because of the part of the documentation which says the values for monorepo >> include need to be relative to project root;

Note: these values need to be relative to project root