bugraoz93 commented on PR #57209: URL: https://github.com/apache/airflow/pull/57209#issuecomment-3447801629
> Ah I have not seen that one and merged mine.. Closing this one. > > > Do we specifically need uv.lock for breeze 🤔 I don't think it is needed. We don't have in any other one > > Yes. Breeze is where we are testing `uv.lock` being committed to the repo. We are also going to make `uv.lock` for Airflow and use it to generate constraints, but I want to keep things running with `uv.lock` in breeze and `auto upgrade` using breeze to see if it does not introduce any unexpected friction in the development process. > > Uv lock is upgraded automatically by the `prek upgrade-important-versions` and when you start locally breeze, it will run appropriate `uv tool upgrade` to make sure that latest version is used and that it uses the uv.lock file -> this gives better reproducibility of the local breeze installation. I am planning to do the same for the whole Airflow workspace. There `uv sync --locked` should bring the environment to the **exact** locked version we will have in the repo. > > But that requires some changes to the way how we generate and use constraints. This also deleted the `uv.lock`, so I wasn't fully sure about merging and waited to double-check. Good to hear you merged one without the `uv.lock` change. Thanks for the details! It makes sense! Could make things more stable and the upgrades are already automated, so no need to worry about the operational side of managing `uv.lock` -- 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]
