Skip to content

Conversation

@amoghrajesh
Copy link
Contributor

Ideally, we should be nuking this away from the provider in the next provider wave (major) and use it from task SDK. This will eventually go away when we decouple sdk and core and providers can truly depend on sdk.


^ 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.

@amoghrajesh amoghrajesh force-pushed the add-deprecation-for-getcurrentcontext branch from a1101eb to 9fef580 Compare May 9, 2025 06:07
@amoghrajesh amoghrajesh merged commit cfdf63e into apache:main May 9, 2025
64 checks passed
@amoghrajesh amoghrajesh deleted the add-deprecation-for-getcurrentcontext branch May 9, 2025 08:55
potiuk added a commit to potiuk/airflow that referenced this pull request May 9, 2025
The apache#50301 deprecated using get_current_context in standard provider
in favour of the task.sdk call, but some core tests are still
using the provider's one.
potiuk added a commit to potiuk/airflow that referenced this pull request May 9, 2025
The apache#50301 deprecated using get_current_context in standard provider
in favour of the task.sdk call, but some core tests are still
using the provider's one.
potiuk added a commit to potiuk/airflow that referenced this pull request May 9, 2025
The apache#50301 deprecated using get_current_context in standard provider
in favour of the task.sdk call, but some core tests are still
using the provider's one.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants