-
Notifications
You must be signed in to change notification settings - Fork 15.1k
Sync v3-0-stable
with v3-0-test
to release 3.0.1
#50247
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
Conversation
The separation of docs missed the substitution to replace version in some documentation. (cherry picked from commit 8b6b9b9) Fixes: #49622 Co-authored-by: Jarek Potiuk <[email protected]>
…_triggers (#46303) This PR adds a STRAIGHT_JOIN hint to prevent an unintended full scan of TaskInstance table in get_sorted_triggers. With MySQL backend, if there are many records in the trigger, it causes the task_instance to be scanned first as the driving table, leading to slow queries. (cherry picked from commit 9f0ac9a)
This was obsoleted by logging changes in task sdk, but its removal was missed, it seems. (cherry picked from commit adffb47)
(cherry picked from commit eca6a53)
Co-authored-by: Shubham Raj <[email protected]> (cherry picked from commit c862e21)
This is required for async sqlalchemy operations. This surfaces e.g. when we install with `--no-dev` and run the api-server, we'll get missing module `greenlet` error in api-server logs. (cherry picked from commit 0c30c6e)
It is assumed by the migration process that there will not be any dag_code records that don't have a serdag record. It seems this only happens when there are two files with the same dag id. --------- Co-authored-by: Tzu-ping Chung <[email protected]> (cherry picked from commit 4202418)
(cherry picked from commit d17ca5c)
(cherry picked from commit c970317)
In 2.x, it was expected that this field was valid json -- e.g. `"0 0 * * *"`. In 3.x, the column is renamed and repurposed and not json. So if we downgrade it, we need to null it out. It will get updated when dag is reserialized. If we *don't* do this, the scheduler crashes. (cherry picked from commit 1bad247)
(cherry picked from commit 3a6b821)
(cherry picked from commit d391a6d)
3.0.0 is out 🎉 (cherry picked from commit bf47ede)
Bumps [@babel/runtime](https://github.com/babel/babel/tree/HEAD/packages/babel-runtime) from 7.26.0 to 7.27.0. - [Release notes](https://github.com/babel/babel/releases) - [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md) - [Commits](https://github.com/babel/babel/commits/v7.27.0/packages/babel-runtime) --- updated-dependencies: - dependency-name: "@babel/runtime" dependency-version: 7.27.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> (cherry picked from commit 51e242c)
(cherry picked from commit 0d31f33)
) (cherry picked from commit 1bcbe8f)
(cherry picked from commit 19a113e)
(cherry picked from commit 3b611be)
(cherry picked from commit 66750fd)
* Fixing upgrade checks on main * reuse variable (cherry picked from commit bf2846b)
…ration (#49614) * update how to docs to convert plugins to airflow3 * Update airflow-core/docs/installation/upgrading_to_airflow3.rst Co-authored-by: Pierre Jeambrun <[email protected]> * update docs --------- Co-authored-by: Pierre Jeambrun <[email protected]> (cherry picked from commit 02b6eb6)
(cherry picked from commit 39f445d)
* Add backcompat shim for get_current_context * use sdk! Co-authored-by: Kaxil Naik <[email protected]> --------- Co-authored-by: Kaxil Naik <[email protected]> (cherry picked from commit 59260fe)
The support we added isn't a "workaround", its absolutely intentional. It's just deprecated :) (cherry picked from commit 924f3fd)
This removes examples for FAB/Flask Airflow 2 style plugins, and adds an section about the compatibility later in the FAB provider. (cherry picked from commit cf16f69)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rubber stamped, too big to do anything else
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is huge, joining with ash on the rubber stamp. Looks like a lot of stuff we fixed in 3.0.1! WOW!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually went through all commits to see if I can spot anything suspicious. I did not find anything.
Looks good.
🎉 |
This PR Syncs
v3-0-stable
withv3-0-test
to release 3.0.1.Release notes and version bumps added in:
Changes between Airflow 3.0.0 and 3.0.1
Listed in 5e37a2f
Changes between Task SDK 1.0.0 and 1.0.1
map_index_template
on task completion #49809)state
attribute toRuntimeTaskInstance
#50031)@task.kuberenetes_cmd
#46913)^ 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.