mistercrunch commented on issue #29836: URL: https://github.com/apache/superset/issues/29836#issuecomment-2863829675
> A check for ensuring that any added migrations/versions are newer than the latest one in master should probably prevent PR from merging if not true I thought it was already the case and I'm still confused as to what the exact issue is. Presumably there are out-of-order migrations in one of the micro releases (?) Maybe in `3.0.1` ? If that's the case, presumable it would only affect people who didn't skip `3.0.1`. Won't have time to test, but if that's the case, the steps for repro would be something like: - nuke the database - pull tag 3.0.0 and build/start - pull tag 3.0.1 and build/start - pull tag 4.1.2 and build/start The last step here should hit this issue (?) Assuming this is all true, the fix would be to identify the release with out-of-order migrations (seems it may be 3.0.1) and alter the ids to align with what's in the following relesease -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
