shahar1 commented on code in PR #75209:
URL: https://github.com/apache/airflow/pull/75209#discussion_r4329779202
##########
providers/databricks/docs/changelog.rst:
##########
@@ -26,6 +26,31 @@
Changelog
---------
+7.22.1
+......
+
+.. note::
+
+ Query lineage now uses the OpenLineage public API. The
``jobType.integration`` job facet
Review Comment:
The note should also say that the `openlineage` extra floor moves from 2.3.0
to 2.16.0. `require_openlineage_version(provider_min_version="2.16.0")` now
skips query lineage (it only logs) on older OpenLineage providers, so users on
2.5–2.15 lose query lineage until they upgrade. Also: is a patch release
(7.22.1) right for a change that, as this note says, needs lineage consumers to
update their filters?
##########
providers/snowflake/docs/changelog.rst:
##########
@@ -27,6 +27,44 @@
Changelog
---------
+6.20.0
+......
+
+.. note::
+
+ The Cortex Agent hook and operator modules are now ``hooks.cortex_agent``
and
+ ``operators.cortex_agent``, and the SQL API hook module is
``hooks.sql_api`` under
+ ``airflow.providers.snowflake``. Previously released imports continue to
work with
+ deprecation warnings. SQLAlchemy must be below 2.1 for compatibility with
snowflake-sqlalchemy.
+
+ Query lineage now uses the OpenLineage public API. The
``jobType.integration`` job facet
Review Comment:
Same as Databricks: please mention the `openlineage` extra floor 2.3.0 →
2.16.0. On OpenLineage providers older than 2.16.0, query lineage is now
skipped with only a log line.
##########
providers/alibaba/docs/changelog.rst:
##########
@@ -26,6 +26,17 @@
Changelog
---------
+3.5.2
+.....
+
+Misc
+~~~~
+
+* ``Allow reading remote logs without a task instance (#73580)``
Review Comment:
In this provider #73580 only changes the `OSSRemoteLogIO.read` annotation
from `RuntimeTI` to `RuntimeTI | None`. Behaviour does not change, so "Allow
reading remote logs without a task instance" claims too much. The Amazon and
Azure entries describe the same diff as type hints. Use that wording, or move
the entry to the excluded block. In that case this release has nothing
user-facing left.
##########
providers/openai/docs/changelog.rst:
##########
@@ -20,6 +20,22 @@
Changelog
---------
+2.2.0
+.....
+
+Features
+~~~~~~~~
+
+* ``Add async aget_conn and acreate_embeddings to OpenAIHook (#74149)``
+
+Bug Fixes
+~~~~~~~~~
+
+* ``Require common.compat 1.21.0 for asynchronous OpenAI hook helpers
(#74933)``
Review Comment:
The content is accurate, since #74149 imports `get_async_extra_dejson`,
which first shipped in common.compat 1.21.0. A dependency floor is Misc,
though. Because #74149 is also unreleased, this could be one entry: ``Add async
aget_conn and acreate_embeddings to OpenAIHook (#74149, #74933)``.
##########
providers/fab/docs/changelog.rst:
##########
@@ -20,6 +20,37 @@
Changelog
---------
+3.10.2
+......
+
+Bug Fixes
+~~~~~~~~~
+
+* ``Distinguish invalid Dag access control from FAB permission backend
failures (#74788)``
+* ``Check all names before airflow roles import writes anything (#74711)``
+* ``Keep the /auth mount path when ProxyFix applies X-Forwarded-Prefix
(#74603)``
+* ``Sync Dag permissions for CustomAuthManager (#74022)``
+
+Misc
+~~~~
+
+* ``Support SQLAlchemy 2.1 typing in permission sorting (#75075)``
+* ``Bump prettier to 3.9.10 (#74765)``
+* ``Bump @babel/core, @babel/eslint-parser and @babel/preset-env to 8.0.7
(#74670)``
+
+Doc-only
+~~~~~~~~
+
+* ``Fix missing and incorrect endpoints in the API permission reference
(#74871)``
+* ``Scope asset-wide queued event deletion to editable Dags (#74839)``
Review Comment:
This describes the core API change. The FAB part of #74839 only removes the
`DELETE /api/v2/assets/{asset_id}/queuedEvents` → `DAGs.can_edit` row from the
permission reference. Suggest: ``Remove the asset-wide queued event deletion
row from the API permission reference (#74839)``.
##########
providers/vespa/docs/changelog.rst:
##########
@@ -25,11 +25,22 @@
Changelog
---------
+0.2.0
+.....
+
.. note::
The provider now supports Python 3.14. On 3.14 it requires
``pyvespa>=1.2.9``, the first release to
allow Python 3.14: every earlier release caps itself at ``<3.14``, which was
why the provider was
excluded from it. Python 3.11-3.13 keep ``pyvespa>=1.1.2``, so nothing is
forced to upgrade there.
+Features
+~~~~~~~~
+
+* ``Support Python 3.14 with pyvespa 1.2.9 (#74559, #75062)``
Review Comment:
0.1.2 already declared Python 3.14 (`Programming Language :: Python ::
3.14`, `requires-python = ">=3.11"`), and the #74559 exclusion was never
released. The net change is `pyvespa>=1.2.9; python_version >= '3.14'`. Suggest
moving this to Bug Fixes as ``Require pyvespa 1.2.9 or newer on Python 3.14
(#74559, #75062)`` and releasing it as 0.1.3. On a 0.x provider, 0.2.0 reads as
a breaking release with no note.
##########
providers/apache/tinkerpop/docs/changelog.rst:
##########
@@ -18,6 +18,17 @@
``apache-airflow-providers-apache-tinkerpop``
+1.2.2
+.....
+
+Bug Fixes
+~~~~~~~~~
+
+* ``Exclude unsupported Python 3.14 from Apache TinkerPop (#74559)``
Review Comment:
1.2.1 declared Python 3.14. This patch adds `!=3.14.*` to `requires-python`,
so on 3.14 pip resolves to 1.2.1. A short note would explain why.
##########
providers/google/docs/changelog.rst:
##########
@@ -27,6 +27,54 @@
Changelog
---------
+22.8.0
+......
+
+.. note::
+
+ On Airflow 3.3 and later, killing a deferred Dataflow template,
flex-template or YAML task
+ now cancels its job by default. Set ``cancel_on_kill=False`` to leave it
running.
+ For flex-template and YAML operators, use ``drain_pipeline=True`` to drain
a streaming
+ job instead of cancelling it.
+
+ ``BigQueryToGCSOperator`` now also cancels synchronous extract jobs when
its task is killed.
+ Set ``cancel_on_kill=False`` to leave the job running. A cancelled job
cannot be reattached
+ with ``force_rerun=False``; use ``force_rerun=True`` when retries should
submit a new job.
+
+Features
+~~~~~~~~
+
+* ``Add retry-safe batch_id_prefix to DataprocCreateBatchOperator (#69855)``
+
+Bug Fixes
+~~~~~~~~~
+
+* ``Preserve HTTPError for Dataprep responses with non-JSON error bodies
(#71702)``
+* ``Honor execution_timeout in deferrable GKEStartPodOperator tasks (#71528)``
+* ``Guard BigQuery job cancellation before hook initialization (#74946)``
+* ``Handle remote-log reads without a task instance (#73580)``
+* ``Warn when ignore_unknown_values cannot drop fields during BigQuery schema
autodetection (#71675)``
+* ``Use the default Google console domain for an empty environment value
(#70067)``
+* ``Allow GKE Autopilot clusters without node pools and preserve pod finish
actions after deferral (#69876)``
+* ``Avoid Vertex AI Feature Store imports during Dag parsing (#69823)``
+* ``Cancel Dataflow jobs when deferred tasks are killed (#69586)``
+* ``Cancel BigQuery extract jobs when BigQueryToGCSOperator tasks are killed
(#74564)``
+
+Misc
+~~~~
+
+* ``Update Google client dependency minimum versions (#73822)``
Review Comment:
Please name the packages, as the FAB and Edge bump entries do:
google-api-python-client 2.194.0, google-cloud-bigtable 2.36.0,
google-cloud-dataflow-client 0.13.0, google-cloud-dlp 3.36.0,
google-cloud-pubsub 2.37.0, google-cloud-spanner 3.65.0,
google-cloud-texttospeech 2.36.0, google-cloud-translate 3.26.0.
##########
providers/apache/hdfs/docs/changelog.rst:
##########
@@ -27,6 +27,17 @@
Changelog
---------
+4.14.2
+......
+
+Misc
+~~~~
+
+* ``Allow reading remote logs without a task instance (#73580)``
Review Comment:
Same as alibaba: `HdfsRemoteLogIO.read` only gets a `RuntimeTI | None`
annotation, and behaviour does not change.
--
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]
