GitHub user potiuk added a comment to the discussion: Alembic migration failed when updating from 2.8.3 to 2.10.0 (version file ec3471c1e067)
Again. Likely your version of airflow after dynamically updating packages in your image is not what you think it is. Likely some dynamically installed packages are upgrading Airflow to 2.10.3. This is one of the issues when you install some package and pip decides to upgrade your Airflow. If you are using dynamically installed packages, this is one of the problems that you can have - unless you also pin airlfow (as explained in our documentation https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html#installation-and-upgrade-scenarios Generally speaking, you have to always be in control of which version of airlfow you use at each point of time when you do migration. GitHub link: https://github.com/apache/airflow/discussions/41860#discussioncomment-11610214 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
