2.2.0 Hotfix #1432
Merged
2.2.0 Hotfix #1432
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Woohoo @yogeshojha! 🎉 You've just dropped some hot new code! 🔥 Hang tight while we review this! You rock! 🤘 |
1 similar comment
|
Woohoo @yogeshojha! 🎉 You've just dropped some hot new code! 🔥 Hang tight while we review this! You rock! 🤘 |
|
Holy smokes! 🤯 You've just made reNgine even more awesome! Your code is now part of the reNgine hall of fame. 🏆 Keep the cool ideas coming - maybe next time you'll break the internet! 💻💥 Virtual high fives all around! 🙌 |
1 similar comment
|
Holy smokes! 🤯 You've just made reNgine even more awesome! Your code is now part of the reNgine hall of fame. 🏆 Keep the cool ideas coming - maybe next time you'll break the internet! 💻💥 Virtual high fives all around! 🙌 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
reNgine 2.2.0 while upgrading from 2.1.3 had issues with migrations, because I created new 0001_initial.py migrations.
Thank you @ncharron for pointing out this mistake, all 0001_initial migrations have been rolled back to 2.1.3 and new migrations have been created for change in models.
This should fix any issue with migration happening now on 2.2.0