potiuk commented on code in PR #67920:
URL: https://github.com/apache/airflow/pull/67920#discussion_r3344813730


##########
providers/amazon/docs/changelog.rst:
##########
@@ -26,6 +26,44 @@
 Changelog
 ---------
 
+9.30.0
+......
+
+Features
+~~~~~~~~
+
+* ``Add 'GlueCatalogBatchDeletePartitionOperator' (#66721)``
+* ``Fix inconsistency in S3 transfer operators (#67378)``
+* ``Add 'OpenSearchServerlessCreateCollectionOperator' (#66549)``
+* ``Propogate 'verify' and 'botocore_config' in batch triggers (#67508)``
+* ``Add ExecuteCallback support to AWS ECS Executor (#63657)``
+* ``fix: Support log level parsing from container output in 
'EcsRunTaskOperator' (#67180)``

Review Comment:
   It's a bug fix — the commit is `fix:`-prefixed — so I moved it to **Bug 
Fixes** as `Support log level parsing from container output in 
'EcsRunTaskOperator' (#67180)`.
   
   ---
   Drafted-by: Claude Code (Opus 4.8); reviewed by @potiuk before posting



##########
providers/amazon/docs/changelog.rst:
##########
@@ -26,6 +26,44 @@
 Changelog
 ---------
 
+9.30.0
+......
+
+Features
+~~~~~~~~
+
+* ``Add 'GlueCatalogBatchDeletePartitionOperator' (#66721)``
+* ``Fix inconsistency in S3 transfer operators (#67378)``
+* ``Add 'OpenSearchServerlessCreateCollectionOperator' (#66549)``
+* ``Propogate 'verify' and 'botocore_config' in batch triggers (#67508)``
+* ``Add ExecuteCallback support to AWS ECS Executor (#63657)``
+* ``fix: Support log level parsing from container output in 
'EcsRunTaskOperator' (#67180)``
+
+Bug Fixes
+~~~~~~~~~
+
+* ``Fix SageMaker processing stopped state handling (#67291)``
+* ``Fix EMR Serverless task failure on transient AWS throttling errors 
(#67222)``
+* ``Fix duplicated logs and memory issue with S3 log handler (#67144)``
+* ``fix: EksPodOperator 401 with cross-account AssumeRole via aws_conn_id 
(#65335)``

Review Comment:
   Done — beautified to `Fix EksPodOperator 401 with cross-account AssumeRole 
via aws_conn_id (#65335)`.
   
   ---
   Drafted-by: Claude Code (Opus 4.8); reviewed by @potiuk before posting



##########
providers/apache/drill/docs/changelog.rst:
##########
@@ -26,6 +26,20 @@
 Changelog
 ---------
 
+3.3.3
+.....
+
+Misc
+~~~~
+
+* ``Add explicit [tool.flit.sdist] sections to flit-based pyproject.tomls 
(#65861)``

Review Comment:
   You're right — moved `Add explicit [tool.flit.sdist] sections to flit-based 
pyproject.tomls (#65861)` to the excluded block. That left 3.3.3 with an empty 
changelog, so I promoted the DAG→Dag wording change (#66153) into a 
**Doc-only** section — drill 3.3.3 now ships as a doc-only release.
   
   ---
   Drafted-by: Claude Code (Opus 4.8); reviewed by @potiuk before posting



##########
providers/apache/drill/docs/changelog.rst:
##########
@@ -26,6 +26,20 @@
 Changelog
 ---------
 
+3.3.3
+.....
+
+Misc
+~~~~
+
+* ``Add explicit [tool.flit.sdist] sections to flit-based pyproject.tomls 
(#65861)``

Review Comment:
   Followed the kafka convention — `#65861` is now in the excluded block.
   
   ---
   Drafted-by: Claude Code (Opus 4.8); reviewed by @potiuk before posting



##########
providers/common/ai/docs/changelog.rst:
##########


Review Comment:
   🎉 Thanks!
   
   ---
   Drafted-by: Claude Code (Opus 4.8); reviewed by @potiuk before posting



##########
providers/edge3/docs/changelog.rst:
##########
@@ -27,6 +27,42 @@
 Changelog
 ---------
 
+3.8.0
+.....
+
+.. note::
+    This release of the Edge provider requires Apache Airflow 3.3+; the new 
execute-callback worker support (#67679) relies on APIs available only in 
Airflow 3.3 and later.

Review Comment:
   Reworded the note: the new execute-callback worker support (#67679) needs 
Apache Airflow 3.3+, while the Edge provider itself still supports 3.0+ — the 
feature is simply inactive on older releases.
   
   ---
   Drafted-by: Claude Code (Opus 4.8); reviewed by @potiuk before posting



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to