From 8dfdc3a0a8aa4a12f0e0e3f6e0a6ff925646c201 Mon Sep 17 00:00:00 2001 From: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> Date: Sat, 27 Apr 2024 09:56:48 -0400 Subject: [PATCH] Move significant note for past release to release notes (#39283) Once the release is out, these should be added directly to the release notes - newsfragments are all about future releases! --- RELEASE_NOTES.rst | 8 ++++++++ airflow/reproducible_build.yaml | 4 ++-- newsfragments/38015.significant.rst | 6 ------ 3 files changed, 10 insertions(+), 8 deletions(-) delete mode 100644 newsfragments/38015.significant.rst diff --git a/RELEASE_NOTES.rst b/RELEASE_NOTES.rst index 5533fad32cc30..1f323919ea04e 100644 --- a/RELEASE_NOTES.rst +++ b/RELEASE_NOTES.rst @@ -111,6 +111,14 @@ Xcom table column ``value`` type has changed from ``blob`` to ``longblob``. This To downgrade from revision: ``b4078ac230a1``, ensure that you don't have Xcom values larger than 65,535 bytes. Otherwise, you'll need to clean those rows or run ``airflow db clean xcom`` to clean the Xcom table. +Stronger validation for key parameter defaults in taskflow context variables (#38015) +""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" + +As for the taskflow implementation in conjunction with context variable defaults invalid parameter orders can be +generated, it is now not accepted anymore (and validated) that taskflow functions are defined with defaults +other than ``None``. If you have done this before you most likely will see a broken DAG and a error message like +``Error message: Context key parameter my_param can't have a default other than None``. + New Features """""""""""" - Allow users to write dag_id and task_id in their national characters, added display name for dag / task (v2) (#38446) diff --git a/airflow/reproducible_build.yaml b/airflow/reproducible_build.yaml index fc6a3933e825b..c6683aa2c04e4 100644 --- a/airflow/reproducible_build.yaml +++ b/airflow/reproducible_build.yaml @@ -1,2 +1,2 @@ -release-notes-hash: 416d01241f2b6ed259e8d991fb7ac1f8 -source-date-epoch: 1712672348 +release-notes-hash: aad86522e49984ce17db1b8647cfb54a +source-date-epoch: 1714165337 diff --git a/newsfragments/38015.significant.rst b/newsfragments/38015.significant.rst deleted file mode 100644 index c6398da90a835..0000000000000 --- a/newsfragments/38015.significant.rst +++ /dev/null @@ -1,6 +0,0 @@ -Stronger validation for key parameter defaults in taskflow context variables - -As for the taskflow implementation in conjunction with context variable defaults invalid parameter orders can be -generated, it is now not accepted anymore (and validated) that taskflow functions are defined with defaults -other than ``None``. If you have done this before you most likely will see a broken DAG and a error message like -``Error message: Context key parameter my_param can't have a default other than None``.