What is your suggestion?

When a package, that is built using artifacts from other packages, can be built, but completely isolating the transitive dependencies. For consumers of that package, the transitive dependencies will not exist.

This might be a useful mechanism for releasing, both internally, but also externally (to other users) without unveiling the internal packages.

I can see at least some custom commands that could implement this via user-side (collect binaries + re-package), but it could be interesting what a --build=missing means for this kind of package, how the information from dependencies is gathered, how the package_id can be computed while isolating the dependencies.

Have you read the CONTRIBUTING guide?

• I've read the CONTRIBUTING guide