-
Notifications
You must be signed in to change notification settings - Fork 16.4k
[v3-1-test] Fix airflow/task-sdk relase PMC checks (#59164) #59165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
There were few small issues with the airflow/task-sdk release-checks: * one cd was missing in the process * task-sdk folder was not pointing to the right sub-folder. * Dockerfile.pmc should use constraints and for task-sdk they should install also apache-airflow and apache-airflow-core as those are not dependencies of task-sdk and pip failed to find them without --pre flag. (cherry picked from commit ad6961d) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Member
Author
|
I cherry-picked a bit more changes (not cherry-picked so far) - from provider changes, this will make any future cherry-picks to breeze release process a bit easier (less conflicts) |
Contributor
|
cool! Thanks! |
ephraimbuddy
pushed a commit
that referenced
this pull request
Dec 8, 2025
There were few small issues with the airflow/task-sdk release-checks: * one cd was missing in the process * task-sdk folder was not pointing to the right sub-folder. * Dockerfile.pmc should use constraints and for task-sdk they should install also apache-airflow and apache-airflow-core as those are not dependencies of task-sdk and pip failed to find them without --pre flag. (cherry picked from commit ad6961d)
ephraimbuddy
pushed a commit
that referenced
this pull request
Dec 8, 2025
There were few small issues with the airflow/task-sdk release-checks: * one cd was missing in the process * task-sdk folder was not pointing to the right sub-folder. * Dockerfile.pmc should use constraints and for task-sdk they should install also apache-airflow and apache-airflow-core as those are not dependencies of task-sdk and pip failed to find them without --pre flag. (cherry picked from commit ad6961d)
ephraimbuddy
pushed a commit
that referenced
this pull request
Dec 8, 2025
There were few small issues with the airflow/task-sdk release-checks: * one cd was missing in the process * task-sdk folder was not pointing to the right sub-folder. * Dockerfile.pmc should use constraints and for task-sdk they should install also apache-airflow and apache-airflow-core as those are not dependencies of task-sdk and pip failed to find them without --pre flag. (cherry picked from commit ad6961d)
ephraimbuddy
pushed a commit
that referenced
this pull request
Dec 8, 2025
There were few small issues with the airflow/task-sdk release-checks: * one cd was missing in the process * task-sdk folder was not pointing to the right sub-folder. * Dockerfile.pmc should use constraints and for task-sdk they should install also apache-airflow and apache-airflow-core as those are not dependencies of task-sdk and pip failed to find them without --pre flag. (cherry picked from commit ad6961d)
ephraimbuddy
pushed a commit
that referenced
this pull request
Dec 8, 2025
There were few small issues with the airflow/task-sdk release-checks: * one cd was missing in the process * task-sdk folder was not pointing to the right sub-folder. * Dockerfile.pmc should use constraints and for task-sdk they should install also apache-airflow and apache-airflow-core as those are not dependencies of task-sdk and pip failed to find them without --pre flag. (cherry picked from commit ad6961d)
ephraimbuddy
pushed a commit
that referenced
this pull request
Dec 9, 2025
There were few small issues with the airflow/task-sdk release-checks: * one cd was missing in the process * task-sdk folder was not pointing to the right sub-folder. * Dockerfile.pmc should use constraints and for task-sdk they should install also apache-airflow and apache-airflow-core as those are not dependencies of task-sdk and pip failed to find them without --pre flag. (cherry picked from commit ad6961d)
ephraimbuddy
pushed a commit
that referenced
this pull request
Dec 11, 2025
There were few small issues with the airflow/task-sdk release-checks: * one cd was missing in the process * task-sdk folder was not pointing to the right sub-folder. * Dockerfile.pmc should use constraints and for task-sdk they should install also apache-airflow and apache-airflow-core as those are not dependencies of task-sdk and pip failed to find them without --pre flag. (cherry picked from commit ad6961d)
ephraimbuddy
pushed a commit
that referenced
this pull request
Dec 12, 2025
There were few small issues with the airflow/task-sdk release-checks: * one cd was missing in the process * task-sdk folder was not pointing to the right sub-folder. * Dockerfile.pmc should use constraints and for task-sdk they should install also apache-airflow and apache-airflow-core as those are not dependencies of task-sdk and pip failed to find them without --pre flag. (cherry picked from commit ad6961d)
ephraimbuddy
pushed a commit
that referenced
this pull request
Jan 6, 2026
There were few small issues with the airflow/task-sdk release-checks: * one cd was missing in the process * task-sdk folder was not pointing to the right sub-folder. * Dockerfile.pmc should use constraints and for task-sdk they should install also apache-airflow and apache-airflow-core as those are not dependencies of task-sdk and pip failed to find them without --pre flag. (cherry picked from commit ad6961d)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:dev-tools
backport-to-v3-1-test
Mark PR with this label to backport to v3-1-test branch
changelog:skip
Changes that should be skipped from the changelog (CI, tests, etc..)
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.
There were few small issues with the airflow/task-sdk release-checks:
^ 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.