ephraimbuddy commented on code in PR #62857:
URL: https://github.com/apache/airflow/pull/62857#discussion_r2894261902


##########
RELEASE_NOTES.rst:
##########
@@ -24,6 +24,111 @@
 
 .. towncrier release notes start
 
+Airflow 3.1.8 (2026-03-10)
+--------------------------
+
+Significant Changes
+^^^^^^^^^^^^^^^^^^^
+
+Backfill permissions are now handled via ``DagAccessEntity.Run`` (#61456)
+""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+``is_authorized_backfill`` of the ``BaseAuthManager`` interface has been 
removed. Core will no longer call this method and their
+provider counterpart implementation will be marked as deprecated.
+Permissions for backfill operations are now checked against the 
``DagAccessEntity.Run`` permission using the existing
+``requires_access_dag`` decorator. In other words, if a user has permission to 
run a DAG, they can perform backfill operations on it.
+
+Please update your security policies to ensure that users who need to perform 
backfill operations have the appropriate ``DagAccessEntity.Run`` permissions. 
(Users
+having the Backfill permissions without having the DagRun ones will no longer 
be able to perform backfill operations without any update)
+
+Bug Fixes
+^^^^^^^^^
+- Fix: Elasticsearch is now fully compatible with remote logging along side 
with ``apache-airflow-providers-elasticsearch>=6.5.0``. Please review 
elasticsearch provider release notes for more information 
https://airflow.apache.org/docs/apache-airflow-providers-elasticsearch/6.5.0/changelog.html
 (#62121) (#62940)

Review Comment:
   ```suggestion
   - Fix: Elasticsearch is now fully compatible with remote logging along side 
with ``apache-airflow-providers-elasticsearch>=6.5.0``(#62121) (#62940)
   ```
   This information is enough or you can add it to significant changes



-- 
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