Thanks for the reply, there’s also another conflicting scenario aside from testing new engine.
For example, common library “a” is developed using version 1.4. There’s a game that is base off version 1.4 that already went live. When we have a new project that based off version 1.5 and still use library a. Library a meta file would be forced to update. If git submodules is used, there would be some problem.
There’s a few ways around this now, branch/tag common library “a” with version tag so that projects that uses it pull specific version tags based on which engine version they are based of. But it’s tedious and lots of unnecessary work.