This is an automated email from the ASF dual-hosted git repository.
kaxil pushed a commit to branch v3-4-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v3-4-test by this push:
new bdd847f5b5d [v3-4-test] Fix upgrade guide sections showing as separate
pages in the docs sidebar (#75468) (#75470)
bdd847f5b5d is described below
commit bdd847f5b5da691ec79a61c5ddefe0a71305ca3b
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Fri Oct 23 14:11:02 2026 +0100
[v3-4-test] Fix upgrade guide sections showing as separate pages in the
docs sidebar (#75468) (#75470)
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.
(cherry picked from commit 09fafbc)
Co-authored-by: Kaxil Naik <[email protected]>
---
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.
