b-anantha commented on issue #29836: URL: https://github.com/apache/superset/issues/29836#issuecomment-2864134589
For me the easiest way to see the problem is doing a diff on the `superset db history` output from 3.0.1 and 4.0.2. There should only be newer versions but we can see that there are 2 that come in in the middle which are the ones that are skipped.  I think anyone that ever got on 3.0.x is affected by this. If they went from -2.x to 3.1.x+ it works out. I'm not too familiar with alembic so not sure about it's branching features but you could adjust the two versions to be idempotent, I don't think they are now, and move them up in version to have any new updates work. If someone doesn't want do a major release bump I'm not sure how that can be solved. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
