DOM-74290 - Update airflow & packaging. Remove unused deps#248
Open
ddl-s-rodriguez wants to merge 1 commit intomasterfrom
Open
DOM-74290 - Update airflow & packaging. Remove unused deps#248ddl-s-rodriguez wants to merge 1 commit intomasterfrom
ddl-s-rodriguez wants to merge 1 commit intomasterfrom
Conversation
8c94e7c to
4e3e27c
Compare
4e3e27c to
f28339b
Compare
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
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.
Link to JIRA
DOM-74290
What issue does this pull request solve?
Airflow dependency is old and implies fixing packaging among other ones which ends up having conflicts for some users
What is the solution?
airflowto a less restrictive version~=2.11(not yet jumping to v3)packaginglib -->>=23.2,<27frozendictversion that showed different versions in therequiresvsdevdevpackage:[Jinja2, nbconvert, packaging, polling2]Testing
Briefly describe how the change was tested. The purpose of this section is that a reviewer can identify a test gap, if any.
e.g. "I ran an upgrade from 4.2 to 4.6".
Pull Request Reminders
References (optional)