|
In platform-core and platform-complete, we currently rely on Okapi interface dependency resolution to provide the list of backend modules that are compatible with the frontend modules pinned in the platform's repository. (excluding backend modules that are not dependencies of any frontend modules). The typical update policy of the platform release branches is to update only patch-level versions of modules. This policy is enforced for frontend modules via the repositories Renovate configuration. However, we have nothing in place to limit the scope of backend module updates to patch releases only or an explicit subset of backend modules since Okapi pulls the latest backend modules that have compatible interfaces with the set of frontend releases. The only way to limit the scope of backend updates to a subset of modules or backend module patch releases is to maintain a list of backend modules compatible with the platform manually which is time consuming and error prone. Is it viable to add a mechanism to Okapi to limit the scope of the backend module changes? Is there a better way to deal with this?
|