Fix automated switching of breeze for Airflow 2 #51430
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When we removed hatch_build.py in Airflow 3 we changed the way how we detect automatically if breeze should be reinstalled when you switch to another directory and it stopped working when you had Airflow 2 checked out (say v2-11-test) - this one brings switching back (should be backported to v2-11-test to also allow switching breeze automatically from v2-11-test branch.
Lee-W
approved these changes
Jun 5, 2025
Backport failed to create: v2-11-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker b09e661 v2-11-testThis should apply the commit to the v2-11-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Jun 5, 2025
…51430) When we removed hatch_build.py in Airflow 3 we changed the way how we detect automatically if breeze should be reinstalled when you switch to another directory and it stopped working when you had Airflow 2 checked out (say v2-11-test) - this one brings switching back (should be backported to v2-11-test to also allow switching breeze automatically from v2-11-test branch. (cherry picked from commit b09e661) Co-authored-by: Jarek Potiuk <[email protected]>
potiuk
added a commit
that referenced
this pull request
Jun 5, 2025
…#51435) When we removed hatch_build.py in Airflow 3 we changed the way how we detect automatically if breeze should be reinstalled when you switch to another directory and it stopped working when you had Airflow 2 checked out (say v2-11-test) - this one brings switching back (should be backported to v2-11-test to also allow switching breeze automatically from v2-11-test branch. (cherry picked from commit b09e661)
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Jun 5, 2025
…1430) When we removed hatch_build.py in Airflow 3 we changed the way how we detect automatically if breeze should be reinstalled when you switch to another directory and it stopped working when you had Airflow 2 checked out (say v2-11-test) - this one brings switching back (should be backported to v2-11-test to also allow switching breeze automatically from v2-11-test branch. (cherry picked from commit b09e661) Co-authored-by: Jarek Potiuk <[email protected]>
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Jun 5, 2025
…1430) When we removed hatch_build.py in Airflow 3 we changed the way how we detect automatically if breeze should be reinstalled when you switch to another directory and it stopped working when you had Airflow 2 checked out (say v2-11-test) - this one brings switching back (should be backported to v2-11-test to also allow switching breeze automatically from v2-11-test branch. (cherry picked from commit b09e661) Co-authored-by: Jarek Potiuk <[email protected]>
potiuk
added a commit
that referenced
this pull request
Jun 5, 2025
…51437) When we removed hatch_build.py in Airflow 3 we changed the way how we detect automatically if breeze should be reinstalled when you switch to another directory and it stopped working when you had Airflow 2 checked out (say v2-11-test) - this one brings switching back (should be backported to v2-11-test to also allow switching breeze automatically from v2-11-test branch. (cherry picked from commit b09e661)
vincbeck
pushed a commit
to potiuk/airflow
that referenced
this pull request
Jun 5, 2025
When we removed hatch_build.py in Airflow 3 we changed the way how we detect automatically if breeze should be reinstalled when you switch to another directory and it stopped working when you had Airflow 2 checked out (say v2-11-test) - this one brings switching back (should be backported to v2-11-test to also allow switching breeze automatically from v2-11-test branch.
vincbeck
pushed a commit
to potiuk/airflow
that referenced
this pull request
Jun 5, 2025
When we removed hatch_build.py in Airflow 3 we changed the way how we detect automatically if breeze should be reinstalled when you switch to another directory and it stopped working when you had Airflow 2 checked out (say v2-11-test) - this one brings switching back (should be backported to v2-11-test to also allow switching breeze automatically from v2-11-test branch.
kaxil
pushed a commit
that referenced
this pull request
Jun 6, 2025
…51437) When we removed hatch_build.py in Airflow 3 we changed the way how we detect automatically if breeze should be reinstalled when you switch to another directory and it stopped working when you had Airflow 2 checked out (say v2-11-test) - this one brings switching back (should be backported to v2-11-test to also allow switching breeze automatically from v2-11-test branch. (cherry picked from commit b09e661)
sanederchik
pushed a commit
to sanederchik/airflow
that referenced
this pull request
Jun 7, 2025
When we removed hatch_build.py in Airflow 3 we changed the way how we detect automatically if breeze should be reinstalled when you switch to another directory and it stopped working when you had Airflow 2 checked out (say v2-11-test) - this one brings switching back (should be backported to v2-11-test to also allow switching breeze automatically from v2-11-test branch.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When we removed hatch_build.py in Airflow 3 we changed the way how we detect automatically if breeze should be reinstalled when you switch to another directory and it stopped working when you had Airflow 2 checked out (say v2-11-test) - this one brings switching back (should be backported to v2-11-test to also allow switching breeze automatically from v2-11-test branch.
^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.