Ask HN: How do you do release management across repositories?

Our product has a rather complex multi-repository setup with a mix of open-source and closed-source components. Most of the open-source components are crates that we publish to Crates.io, though some are released as WASM bundles which we can just push as GitHub Releases. We have an open-source CLI as well as a hosted service that depend on these open-source components, but also a closed source API and web frontend that share dependencies, but which are deployed to our own servers.

As you can imagine, there's quite some overhead in release management for versioning these components and making sure that components are properly updated when one of their dependencies is updated. So how does your company deal with such complexities? What CI solutions are you making use of (we currently use GitHub Actions, but having workflow dependencies between repos is no fun...)? What does your release process look like? Thanks!