Improve upgrade important version hook:

[potiuk]

• we do not have to check Python versions below 3.9 - that significantly speeds up the check

• we run uv sync --resolution highest in dev/breeze when there are some changes - that will make sure that the latest version of dependencies in breeze are captured in the uv.lock file

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[gopidesupavan]

nice update :)

[potiuk]

nice update :)

Yeah. I noticed breeze lock was out of sync after the last change and finally I found a way how we can also make it "eventually consistent".

Thanks to that I have an idea how we can add uv.lock to Airflow and use the .lock instead of constraints for PRs and regular developments (we'd still generate constraints the same way we do now, but we could switch to uv.lock. Let's see how it works - but I think this upgrade-important-versions hook might also be used for that - while we could keep canary build detecting all kind of issues.

[github-actions]

Backport successfully created: v3-0-test

Status	Branch	Result
✅	v3-0-test

[potiuk]

• we do not have to check Python versions below 3.9 - that significantly speeds up the check

• we run uv sync --resolution highest in dev/breeze when there are some changes - that will make sure that the latest version of dependencies in breeze are captured in the uv.lock file

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[gopidesupavan]

nice update :)

[potiuk]

nice update :)

Yeah. I noticed breeze lock was out of sync after the last change and finally I found a way how we can also make it "eventually consistent".

Thanks to that I have an idea how we can add uv.lock to Airflow and use the .lock instead of constraints for PRs and regular developments (we'd still generate constraints the same way we do now, but we could switch to uv.lock. Let's see how it works - but I think this upgrade-important-versions hook might also be used for that - while we could keep canary build detecting all kind of issues.

[github-actions]

Backport successfully created: v3-0-test

Status	Branch	Result
✅	v3-0-test

[potiuk]

• we do not have to check Python versions below 3.9 - that significantly speeds up the check

• we run uv sync --resolution highest in dev/breeze when there are some changes - that will make sure that the latest version of dependencies in breeze are captured in the uv.lock file

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[gopidesupavan]

nice update :)

[potiuk]

nice update :)

Yeah. I noticed breeze lock was out of sync after the last change and finally I found a way how we can also make it "eventually consistent".

Thanks to that I have an idea how we can add uv.lock to Airflow and use the .lock instead of constraints for PRs and regular developments (we'd still generate constraints the same way we do now, but we could switch to uv.lock. Let's see how it works - but I think this upgrade-important-versions hook might also be used for that - while we could keep canary build detecting all kind of issues.

[github-actions]

Backport successfully created: v3-0-test

Status	Branch	Result
✅	v3-0-test

[potiuk]

• we do not have to check Python versions below 3.9 - that significantly speeds up the check

• we run uv sync --resolution highest in dev/breeze when there are some changes - that will make sure that the latest version of dependencies in breeze are captured in the uv.lock file

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[gopidesupavan]

nice update :)

[potiuk]

nice update :)

Yeah. I noticed breeze lock was out of sync after the last change and finally I found a way how we can also make it "eventually consistent".

Thanks to that I have an idea how we can add uv.lock to Airflow and use the .lock instead of constraints for PRs and regular developments (we'd still generate constraints the same way we do now, but we could switch to uv.lock. Let's see how it works - but I think this upgrade-important-versions hook might also be used for that - while we could keep canary build detecting all kind of issues.

[github-actions]

Backport successfully created: v3-0-test

Status	Branch	Result
✅	v3-0-test

[potiuk]

• we do not have to check Python versions below 3.9 - that significantly speeds up the check

• we run uv sync --resolution highest in dev/breeze when there are some changes - that will make sure that the latest version of dependencies in breeze are captured in the uv.lock file

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[gopidesupavan]

nice update :)

[potiuk]

nice update :)

Yeah. I noticed breeze lock was out of sync after the last change and finally I found a way how we can also make it "eventually consistent".

Thanks to that I have an idea how we can add uv.lock to Airflow and use the .lock instead of constraints for PRs and regular developments (we'd still generate constraints the same way we do now, but we could switch to uv.lock. Let's see how it works - but I think this upgrade-important-versions hook might also be used for that - while we could keep canary build detecting all kind of issues.

[github-actions]

Backport successfully created: v3-0-test

Status	Branch	Result
✅	v3-0-test

[potiuk]

• we do not have to check Python versions below 3.9 - that significantly speeds up the check

• we run uv sync --resolution highest in dev/breeze when there are some changes - that will make sure that the latest version of dependencies in breeze are captured in the uv.lock file

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[gopidesupavan]

nice update :)

[potiuk]

nice update :)

Yeah. I noticed breeze lock was out of sync after the last change and finally I found a way how we can also make it "eventually consistent".

Thanks to that I have an idea how we can add uv.lock to Airflow and use the .lock instead of constraints for PRs and regular developments (we'd still generate constraints the same way we do now, but we could switch to uv.lock. Let's see how it works - but I think this upgrade-important-versions hook might also be used for that - while we could keep canary build detecting all kind of issues.

[github-actions]

Backport successfully created: v3-0-test

Status	Branch	Result
✅	v3-0-test

[potiuk]

• we do not have to check Python versions below 3.9 - that significantly speeds up the check

• we run uv sync --resolution highest in dev/breeze when there are some changes - that will make sure that the latest version of dependencies in breeze are captured in the uv.lock file

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[gopidesupavan]

nice update :)

[potiuk]

nice update :)

Yeah. I noticed breeze lock was out of sync after the last change and finally I found a way how we can also make it "eventually consistent".

Thanks to that I have an idea how we can add uv.lock to Airflow and use the .lock instead of constraints for PRs and regular developments (we'd still generate constraints the same way we do now, but we could switch to uv.lock. Let's see how it works - but I think this upgrade-important-versions hook might also be used for that - while we could keep canary build detecting all kind of issues.

[github-actions]

Backport successfully created: v3-0-test

Status	Branch	Result
✅	v3-0-test

[potiuk]

• we do not have to check Python versions below 3.9 - that significantly speeds up the check

• we run uv sync --resolution highest in dev/breeze when there are some changes - that will make sure that the latest version of dependencies in breeze are captured in the uv.lock file

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[gopidesupavan]

nice update :)

[potiuk]

nice update :)

Yeah. I noticed breeze lock was out of sync after the last change and finally I found a way how we can also make it "eventually consistent".

Thanks to that I have an idea how we can add uv.lock to Airflow and use the .lock instead of constraints for PRs and regular developments (we'd still generate constraints the same way we do now, but we could switch to uv.lock. Let's see how it works - but I think this upgrade-important-versions hook might also be used for that - while we could keep canary build detecting all kind of issues.

[github-actions]

Backport successfully created: v3-0-test

Status	Branch	Result
✅	v3-0-test