MadhuTiwari-345 opened a new issue, #60770: URL: https://github.com/apache/airflow/issues/60770
### Apache Airflow version 3.1.6 ### If "Other Airflow 3 version" selected, which one? main (development) ### What happened? In the development workflow for Airflow 3.x, the project has moved toward a decoupled structure where airflow-core and providers are separate distributions . According to the documentation in contributing-docs/07_local_virtualenv.rst, developers should be able to run uv sync within the airflow-core directory to set up a minimal core-only environment. However, this currently fails. There is an explicit TODO in that file stating: TODO(potiuk): This will not work yet until we move some remaining provider tests from airflow-core. For now you need to add all package to install all providers and their dependencies. This cross-dependency forces all developers to install over 80+ providers even when they only intend to work on the core engine, which slows down the environment setup and increases the surface area for dependency conflicts. ### What you think should happen instead? Developers should be able to run uv sync in the airflow-core folder to install only the dependencies needed for core tests. To enable this, the remaining test files that depend on provider code need to be identified and moved from the airflow-core package into the appropriate providers/ sub-directories. ### How to reproduce 1. Clone the current main branch of the Airflow repository. 2. Navigate to the core directory: cd airflow-core. 3. Attempt to synchronize the environment: uv sync. Observe: The process fails or produces an incomplete environment because some tests remaining in this directory require provider-specific modules/dependencies that are not part of the core pyproject.toml . ### Operating System Linux / macOS ### Versions of Apache Airflow Providers _No response_ ### Deployment Other ### Deployment details _No response_ ### Anything else? This task is part of the broader Airflow 3.x architectural transition to strict server/client separation and improved Developer Experience (DX) . I would like to help formalize this task into an issue so we can track the movement of these remaining tests. ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
