Multi repo App dependency - how to resolve dependencies while Publish to environment

[KristofKlein]

Hi,

Lets say I have a "common" App A. That is used as dependency in another App B. So now I can build App A on it's own. Works, I can release it, I can have it pushing its artifacts into Nuget. All well.

Now I have App B. And also this one, can now consume Apps from Nuget ( means it finds App A over there) compiles, builds all good.
However, If I now trigger the release action of App B this only includes the Artifacts produced by App B and not the once it is dependent on.

Question is : if I now trigger "Publish to environment" from App B- will this work? I assume it will miss App A? Or does in the flow happen another "resolve dependency" that will collect the apps ( which might be risky, as the version could have changed in the meantime?) ...
So, what is the best way to work around here? Is it possible to get the dependent Apps into a release?
or do I have to trigger two individual "publish to environment" - once from App A followed by App B ( which would jeopardize our idea of environment/app integrity per repo - as App B is more a kind of "client specific" App).

I don't really want to put all my Apps into a single, multi project repo, as this would lead to all sorts of other challenges.

[KristofKlein]

Let me answer this myself: generateDependencyArtifact is the one I was missing. This makes sure the Artifaces used in the CI/CD are also present as artifact while I release my Client app. Like this I can deploy from App B including App A.