alamb opened a new pull request, #27024:
URL: https://github.com/apache/datafusion/pull/27024

   ## Which issue does this PR close?
   
   - Part of #17071
   - Follow on to #26829
   
   ## Rationale for this change
   
   With #26828, we can now add old release documentation to the version picker 
by updating `docs/source/_static/versions.json`. This PR adds every release 
that has an entry in the [upgrade 
guide](https://datafusion.apache.org/library-user-guide/upgrading/index.html).
   
   ## What changes are included in this PR?
   
   - Adds `54.0.0`, `53.0.0`, `52.0.0`, `51.0.0`, `50.0.0`, `49.0.0`, `48.0.1`, 
`48.0.0`, `47.0.0` and `46.0.0` to the version picker
   - Updates the release Sphinx overlay (`docs/scripts/release/conf.py`) so the 
docs from these older tags build:
     - `html_extra_path` (added in 54.0.0), `html_favicon` (53.0.0) and 
`redirects` (53.0.0) are optional
     - Adds a `generate_nav_html` shim for the sidebar template in releases 
before 51.0.0 (pydata-sphinx-theme renamed it to `generate_toctree_html`)
     - Suppresses `myst.header` and `myst.xref_missing` warnings, which fail 
the 46.0.0 build and can no longer be fixed in the released docs
   
   <img width="1637" height="845" alt="Screenshot 2026-11-01 at 7 54 21 AM" 
src="https://github.com/user-attachments/assets/f6009bc8-4846-463f-9baf-6b7bd11800c9";
 />
   
   ## Are these changes tested?
   
   I ran `docs/scripts/build_versions.sh` locally, and the docs for all 14 
listed versions built successfully. I also spot-checked that the sidebar and 
version switcher render in the 46.0.0, 50.0.0 and 53.0.0 output.
   
   Once merged, `Deploy DataFusion versioned docs` should publish 
https://datafusion.apache.org/versions/<version>/ for each of the new versions 
and rebuild the existing ones.
   
   ## Are there any user-facing changes?
   
   Ten more releases in the version picker.
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to