eladkal commented on code in PR #72834:
URL: https://github.com/apache/airflow/pull/72834#discussion_r3975135822
##########
providers/apache/kafka/docs/changelog.rst:
##########
@@ -27,6 +27,30 @@
Changelog
---------
+2.0.0
+.....
+
+.. note::
+ librdkafka callbacks given as dotted-path strings on a Kafka connection
extra (``error_cb``,
Review Comment:
```suggestion
``librdkafka`` callbacks given as dotted-path strings on a Kafka
connection extra (``error_cb``,
```
i think if that way we can avoid adding librdkafka to spell check excluded
word list
##########
providers/apache/beam/docs/changelog.rst:
##########
@@ -26,6 +26,33 @@
Changelog
---------
+6.2.4
+.....
+
+Misc
+~~~~
+
+* ``Bump minimum apache-beam version to 2.76.0 (#61926, #66952)``
+* ``Fix Apache Beam hook type error with mypy 2.2.0 typeshed (#69946)``
+* ``Add Python 3.14 Support (#63520)``
+* ``Add Apache Airflow Provider Registry (#62261)``
+
+Doc-only
+~~~~~~~~
+
+* ``Update changelog with better wording (#71161)``
+* ``Replace DAG with Dag in the Apache provider documentation (#66153)``
+* ``Fix stale system test documentation links (#65071)``
Review Comment:
not user facing can be hidden from changelog
##########
providers/pagerduty/docs/changelog.rst:
##########
@@ -27,11 +27,25 @@
Changelog
---------
+5.2.7
+.....
+
.. note::
The minimum required version of the ``pagerduty`` SDK is now ``7.0.0``,
which replaced
``httpx`` with ``httpx2``. Deployments pinning an older SDK must upgrade
it alongside this
provider. The provider's own hooks and notifier are unchanged.
+Misc
+~~~~
+
+* ``Require the ''pagerduty'' SDK 7.0.0 or newer (#72111)``
Review Comment:
```suggestion
* ``Require ''pagerduty'' SDK 7.0.0 or newer (#72111)``
```
##########
providers/databricks/docs/changelog.rst:
##########
@@ -36,6 +39,34 @@ Changelog
passing an empty value. The argument-validation errors in this sensor are
also now
``ValueError`` rather than ``AirflowException``.
+Breaking changes
+~~~~~~~~~~~~~~~~
+
+* ``Validate DatabricksSQLStatementsSensor exclusivity at __init__ (#70831)``
Review Comment:
I'm not sure if this is a breaking change?
the init fix is something we are doing to all providers. this is first time
I see this classified as breaking. am I missing something?
--
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]
