How to organize work with two repositories (engine and scripts) with different update frequencies?

When working with two repositories with different update frequencies (for example, engine and scripts), you can organize the process as follows:

• Responsibility separation: engine — stable base, updated infrequently; scripts — active development.
• Using branches and tags: create release tags for the engine so that scripts always refer to a specific stable version.
• Build automation: set up CI/CD to automatically check script compatibility when the engine is updated.
• Versioning: clearly version both repositories to understand which engine versions are compatible with the scripts.
• Documentation: maintain documentation on dependencies and update procedures.

Example: scripts in their repository specify in the configuration the engine version they are compatible with, and when the engine is updated, script testing is triggered.