[airflow] branch main updated: Cleanup core newsfragments (#26224)

[je...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jedcunningham pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new af3a074270 Cleanup core newsfragments (#26224)
af3a074270 is described below

commit af3a07427023d7089f3bc74a708723d13ce3cf73
Author: Jed Cunningham <66...@users.noreply.github.com>
AuthorDate: Wed Sep 7 15:21:39 2022 -0700

    Cleanup core newsfragments (#26224)
    
    We accidentally ended up with one for a provider, and another was missing
    the new auto-regsitration behavior.
---
 newsfragments/25410.significant.rst | 8 ++++----
 newsfragments/25623.improvement.rst | 1 -
 2 files changed, 4 insertions(+), 5 deletions(-)

diff --git a/newsfragments/25410.significant.rst b/newsfragments/25410.significant.rst
index b95c102d99..24b4e43704 100644
--- a/newsfragments/25410.significant.rst
+++ b/newsfragments/25410.significant.rst
@@ -9,7 +9,7 @@ If you previously used the ``@daily`` cron preset, your DAG may have looked like
         dag_id='my_example',
         start_date=datetime(2021, 1, 1),
         schedule_interval='@daily',
-    ) as dag:
+    ):
         ...
 
 Going forward, you should use the ``schedule`` argument instead:
@@ -19,7 +19,7 @@ Going forward, you should use the ``schedule`` argument instead:
         dag_id='my_example',
         start_date=datetime(2021, 1, 1),
         schedule='@daily',
-    ) as dag:
+    ):
         ...
 
 The same is true if you used a custom timetable.  Previously you would have used the ``timetable`` argument:
@@ -29,7 +29,7 @@ The same is true if you used a custom timetable.  Previously you would have used
         dag_id='my_example',
         start_date=datetime(2021, 1, 1),
         timetable=EventsTimetable(event_dates=[pendulum.datetime(2022, 4, 5)]),
-    ) as dag:
+    ):
         ...
 
 Now you should use the ``schedule`` argument:
@@ -39,5 +39,5 @@ Now you should use the ``schedule`` argument:
         dag_id='my_example',
         start_date=datetime(2021, 1, 1),
         schedule=EventsTimetable(event_dates=[pendulum.datetime(2022, 4, 5)]),
-    ) as dag:
+    ):
         ...
diff --git a/newsfragments/25623.improvement.rst b/newsfragments/25623.improvement.rst
deleted file mode 100644
index 4cfa738dc8..0000000000
--- a/newsfragments/25623.improvement.rst
+++ /dev/null
@@ -1 +0,0 @@
-``DatabricksSubmitRunOperator`` now supports ``dbt_task`` to run dbt projects on Databricks.