This message was deleted.

So the state locking is on a per-stack basis so yes you can run them both at the same time even with this turned on. However, if you make a change to stack A that stack B is reliant on, and stack B (for whatever reason) has an older version of whatever comes from stack A, then it'll continue to use that value. I would recommend running them one after the other, rather than concurrently

How can you ensure this, however? Imagine the two stacks relate to two standalone apps, both living in their own repository and being developed by different teams. They are deployed automatically using some CI/CD (e.g. GitHub Actions) completely unaware from each other.

In the same way that you would treat any application that had a dependency on another, communication and ensuring that the old value will still work

Thank you so much for the answer! Really helpful.