Skip to content

docs: Add more past versions to the doc site - #27024

Open
alamb wants to merge 5 commits into
apache:mainfrom
alamb:docs/versions-add-upgrade-guide-versions
Open

alamb wants to merge 5 commits into
apache:mainfrom
alamb:docs/versions-add-upgrade-guide-versions

Conversation

@alamb

@alamb alamb commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

Rationale for this change

This PR adds every release that has an entry in the upgrade guide.

What changes are included in this PR?

  1. Adds the latest version of each major release to the docs site back to 50. Prior to version 50, the templates were different so they don't render correctly so I didn't add them
Screenshot 2026-11-03 at 2 59 42 PM

Builds old versions so old links still stay live:

Screenshot 2026-11-03 at 3 00 15 PM

Are these changes tested?

I ran

docs/scripts/build_versions.sh

And checked it out locally:

uv run --with sphinx-autobuild sphinx-autobuild source build/html --port 8000

Note that once merged, a CI job will rebuild the existing docs

Are there any user-facing changes?

more releases in the version picker.

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, and makes the release Sphinx overlay work with the
conf.py and templates of those older releases.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Nov 2, 2026
@alamb alamb changed the title docs: add all versions with an upgrade guide to the version picker docs: Add more past versions to the doc site Nov 3, 2026
alamb and others added 2 commits November 3, 2026 14:30
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@alamb
alamb marked this pull request as ready for review November 3, 2026 20:05
@github-actions github-actions Bot added the development-process Related to development process of DataFusion label Nov 3, 2026
"preferred": true
},
{
"name": "55.1.0",

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think there is any reason to publish docs for anything other than the most recent version of a patch release, so i removed the 55.1.0 and 55.0.0

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And moved them to the "build but not publish" list in old_versions.json

# under the License.

# Build the documentation for each release listed in docs/source/_static/versions.json
# Build the documentation for releases in

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I went with 2 files to keep the old links working but not show them in the picker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

development-process Related to development process of DataFusion documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant