kunaljubce commented on issue #54609: URL: https://github.com/apache/airflow/issues/54609#issuecomment-4028747692
Hi @potiuk - As I understand we're nearing the airflow 3.2 release, can I start working on this? My high level plan of this solution is to: * Run `uv lock` to generate the `uv.lock` file at the project root level, since we can only have 1 uv lock file for all `pyproject.toml` files. However we continue to maintain the provider specific `pyproject.toml` files right? * Have our `breeze` and regular PR builds (that don't do dependency upgrades) use this `uv.lock` for all CI and local builds, including updates to `upgrade-important-versions` prek hook to use the lock file. * For canary builds and PRs modifying the `pyproject.toml` files, the pre-commit and/or CI checks will continue with `--resolution highest`. -- 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]
