Fix hash for breeze dependencies #32895
Merged
Conversation
This file contains 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
potiuk
force-pushed
the
fix-breeze-dependency-hash
branch
from
e7b58b0
to
fa7c74b
Compare
potiuk
force-pushed
the
fix-breeze-dependency-hash
branch
from
fa7c74b
to
bde8e51
Compare
The apache#32873 has been merged without merging and commiting breeze's hash accounting for changed dependencies, breaking unit tests of breeze. This PR brings hash of breeze back adter running `breeze setup version` manually and commiting the changed hash.
potiuk
force-pushed
the
fix-breeze-dependency-hash
branch
from
bde8e51
to
ba0f2f7
Compare
hussein-awala
approved these changes
Jul 27, 2023
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.
The #32873 has been merged without merging and commiting breeze's hash accounting for changed dependencies, breaking unit tests of breeze.
This PR brings hash of breeze back adter running
breeze setup versionmanually and commiting the changed hash.^ 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 newsfragments.