Skip to content

Conversation

@eladkal
Copy link
Contributor

@eladkal eladkal commented Apr 27, 2025

I didn't remove the references to AIRFLOW_V_2_10_PLUS as part of this PR.
we can do that after the release and specifically after we verify if we do 2.11 or not

Copy link
Contributor

@jscheffl jscheffl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume the respective providers/**/pyproject.toml also need to be adjusted to have >=2.10 as depenedency marked? And then pre-commit would re-generate some other files as well...

Otherwise looks good.

@eladkal eladkal force-pushed the bump branch 3 times, most recently from 69e3613 to 939e244 Compare April 27, 2025 10:17
Copy link
Contributor

@jscheffl jscheffl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good...

@jscheffl
Copy link
Contributor

Looks good...

...except the one small static check... :-D

@potiuk
Copy link
Member

potiuk commented Apr 27, 2025

I didn't remove the references to AIRFLOW_V_2_10_PLUS as part of this PR.
we can do that after the release and specifically after we verify if we do 2.11 or not

You can safely remove it now. It does not matter if we release 2.11 or not. If we decide to release 2.11, we should ADD AIRFLOW_V_2_11_PLUS as a constant - removal of AIRFLOW_V_2_10_PLUS is determined simply by the fact that >=2.10 automatically means that everything is AIRFLOW_V2_10_PLUS, so all the code that is not in the if can be removed and the constant can be removed as well.

@eladkal
Copy link
Contributor Author

eladkal commented Apr 28, 2025

I didn't remove the references to AIRFLOW_V_2_10_PLUS as part of this PR.
we can do that after the release and specifically after we verify if we do 2.11 or not

You can safely remove it now. It does not matter if we release 2.11 or not. If we decide to release 2.11, we should ADD AIRFLOW_V_2_11_PLUS as a constant - removal of AIRFLOW_V_2_10_PLUS is determined simply by the fact that >=2.10 automatically means that everything is AIRFLOW_V2_10_PLUS, so all the code that is not in the if can be removed and the constant can be removed as well.

Will handle the removal separately in parallel. I want to move forward in merge so I can prepare changelogs.
This part is not automated yet so it takes long time

@potiuk
Copy link
Member

potiuk commented Apr 28, 2025

Will handle the removal separately in parallel. I want to move forward in merge so I can prepare changelogs.
This part is not automated yet so it takes long time

Yep. Happy to help.

@eladkal eladkal merged commit 0f573ee into apache:main Apr 28, 2025
96 checks passed
@eladkal eladkal deleted the bump branch April 28, 2025 09:36
mvfc pushed a commit to mvfc/airflow that referenced this pull request Apr 29, 2025
* Bump min Airflow version in providers to 2.10

* exclude msgraph test

* fixes
mvfc pushed a commit to mvfc/airflow that referenced this pull request Apr 29, 2025
* Bump min Airflow version in providers to 2.10

* exclude msgraph test

* fixes
mvfc pushed a commit to mvfc/airflow that referenced this pull request Apr 29, 2025
* Bump min Airflow version in providers to 2.10

* exclude msgraph test

* fixes
jroachgolf84 pushed a commit to jroachgolf84/airflow that referenced this pull request Apr 30, 2025
* Bump min Airflow version in providers to 2.10

* exclude msgraph test

* fixes
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.

6 participants