Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
fix migration #5103
Yep. It should be done before pushing develop after closing the release. I forgot it. It is hardly automated. But I'm absolutely glad it breaks the build, that's the purpose, we just need to be more aware of the CI screen.
About the patch releases, I think it might be correct to be broken initially. I prefer that to introduce a not tested commit or outdated settings by mistake. That variable shouldn't be introduced until the release is frozen.