Repository navigation
Fix upgrade guide sections showing as separate pages in the docs sidebar - #75468
Merged
Merged
Conversation
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.
vatsrahul1001
approved these changes
Oct 23, 2026
kaxil
added a commit
that referenced
this pull request
Oct 23, 2026
…he 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 <kaxilnaik@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In the Installation section of the docs sidebar, "Breaking Changes" and "Manual Dag Runs and
logical_date" appear as separate pages next to "Upgrading to Airflow 3" instead of under it. Both are sections ofupgrading_to_airflow3.rst, but they were underlined with=, the same character as the page title. RST read them as two more top-level titles, so the toctree listed the file three times.This demotes both to
-, the level used by "Step 1" through "Step 8". "Migration guidance" sits under "Manual Dag Runs" and moves from-to^to stay one level below it. Thebreaking-changesanddata-interval-manual-triggeringlabels are unchanged, so existing:ref:links still resolve.The two highlighted entries move from the Installation level (aligned with "Local start for development and testing") to inside "Upgrading to Airflow 3" (aligned with "Step 8").
breeze build-docs apache-airflow)