You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "suii2210 (via GitHub)" <gi...@apache.org> on 2026/01/01 09:30:38 UTC
Re: [I] Replace constraints with uv.lock mechanisms for dev env freeze [airflow]
suii2210 commented on issue #54609:
URL: https://github.com/apache/airflow/issues/54609#issuecomment-3703468591
Hello @potiuk
This seems like a sensible way to improve dev environment setup and reduce noisy PR failures by using a committed uv.lock instead of separate constraints files.
The key challenge will be managing when and how the lockfile gets updated and reviewed, but adding it to the `upgrade-important-versions` CI step sounds reasonable.
Happy to discuss workflows for keeping the lockfile up to date without causing extra churn.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org