This is an automated email from the ASF dual-hosted git repository.

kaxil pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new 09fafbcec98 Fix upgrade guide sections showing as separate pages in 
the docs sidebar (#75468)
09fafbcec98 is described below

commit 09fafbcec981345e9ba87c2916d216b213bf0f12
Author: Kaxil Naik <[email protected]>
AuthorDate: Fri Oct 23 13:34:43 2026 +0100

    Fix upgrade guide sections showing as separate pages in the docs sidebar 
(#75468)
    
    Breaking Changes and Manual Dag Runs used the page title's underline, so
    Sphinx treated them as extra top-level titles and listed them as siblings
    of the upgrade guide in the Installation navigation.
---
 airflow-core/docs/installation/upgrading_to_airflow3.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/airflow-core/docs/installation/upgrading_to_airflow3.rst 
b/airflow-core/docs/installation/upgrading_to_airflow3.rst
index a9c5d67fb8f..d15a7d53e92 100644
--- a/airflow-core/docs/installation/upgrading_to_airflow3.rst
+++ b/airflow-core/docs/installation/upgrading_to_airflow3.rst
@@ -348,7 +348,7 @@ Please consider checking the following things after 
upgrading your Airflow insta
 .. _breaking-changes:
 
 Breaking Changes
-================
+----------------
 
 Some capabilities which were deprecated in Airflow 2.x are not available in 
Airflow 3.
 These include:
@@ -411,7 +411,7 @@ These include:
 .. _data-interval-manual-triggering:
 
 Manual Dag Runs and ``logical_date``
-====================================
+------------------------------------
 
 For scheduled runs, ``logical_date`` and ``data_interval`` are both derived 
from
 the Dag's timetable.
@@ -430,7 +430,7 @@ This matters most for Dags that:
   manual run date
 
 Migration guidance
-------------------
+^^^^^^^^^^^^^^^^^^
 
 If your Dag logic needs the user-specified date for a manual run, use
 ``logical_date`` explicitly.

Reply via email to