Is the migration graph stable?

[ThibaultLemaire]

I've noticed this sentence at the very end of the README:

For now only linear revision history is supported.

I'm not sure I understand what you mean by that. We've made some tests with non-linear dependency graphs, and our migrations seem to be applied correctly.

So, is this something we should worry about, or did you just mean there's no support for squash migrations?

[rooterkyberian]

At some point I had assertion that checked if there is no more than 1 dependency in migration since I wasn't quite sure if everything was covered for them, hence the only "linear revision history" support.

As for is graph stable - execution is always dictated by name order. While there is no plan to change it I guess some new unit tests (of MigrationsGraph.__iter__ at least, including migrations with multiple dependencies) should be added before we can guarantee that this is won't change anytime in the future.