Closed tpazderka closed 5 years ago
You're correct.. Not sure what to do now, release 0.3.2 with the correct dependency tree and hope that not too many people installed 0.3.0 & 0.3.1?
I've released 0.3.2 with the correct dependency tree
This fix works for me, not sure if others might be affected by this.
works both for me: v0.3.1 and 0.3.2
Probably depends on django version.
The renaming of migrations in
0.3.1
can cause applications that already reference this node to break as the dependency no longer exists.The correct fix should have been to change the dependency but not renaming the file as that serves as a reference for other projects.