Upgrade the dev version of Airflow to 2.7.0 #30958
Conversation
boring-cyborg
bot
added
area:production-image
potiuk
requested review from
ephraimbuddy,
jedcunningham,
o-nikolas and
pierrejeambrun
|
We already have a few PRs that have wrongly generated version (#30827 for example) so likely it's a good time to merge 2.6.0.dev0 -> 2.7.0.dev0 :) |
|
Not sure which part of the release process it is in, but it looks like it shoudl be done slightly earlier (i.e. when we cut-off the 2.6.0 branch). |
| # Example: dataset_manager_kwargs = {{"some_param": "some_value"}} | ||
| # dataset_manager_kwargs = | ||
|
|
||
| # (experimental) Whether components should use Airflow Internal API for DB connectivity. |
There was a problem hiding this comment.
Why do we have this change, this seems unrelated ?
There was a problem hiding this comment.
Quite the contrary. They are very much related. They were (correctly) automatically added by pre-commit.
Those parameters have version-added = 2.7.0. This was implemented as part of the feature flags for AIP-44 and AIP-52, but in order to not comploicate it further we restricted automated moving parameters from .yaml to config based on "version-added" > currrent version. We moved the related parameters that were scheduled for 2.7 to have "version-added=2.7.0" so they started to appear only when we moved the version to 2.7.0.
ephraimbuddy
added
the
changelog:skip
4 participants
^ 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.