Skip to content

docs: add 55.2.0 and 54.1.0 to the version picker - #26829

Draft
alamb wants to merge 4 commits into
apache:mainfrom
alamb:docs/versions-add-55.2.0-54.1.0
Draft

alamb wants to merge 4 commits into
apache:mainfrom
alamb:docs/versions-add-55.2.0-54.1.0

Conversation

@alamb

@alamb alamb commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

Rationale for this change

With #26828, adding a release to docs/source/_static/versions.json is all that is needed to publish its documentation. This adds the latest release and backfills one older one.

What changes are included in this PR?

  • Adds 55.2.0 (now preferred) and 54.1.0 to versions.json.

Are these changes tested?

The same change on my fork (alamb#40) triggered the versioned docs workflow, which rebuilt all four listed versions and published them under https://alamb.github.io/datafusion/versions/.

Once merged, Deploy DataFusion versioned docs should publish https://datafusion.apache.org/versions/55.2.0/ and https://datafusion.apache.org/versions/54.1.0/ and rebuild 55.1.0 and 55.0.0.

Are there any user-facing changes?

Two more releases in the version picker, with 55.2.0 as the current stable release.

alamb and others added 2 commits October 27, 2026 16:13
…uild script

Add docs/scripts/build_versions.sh, which builds the documentation for the
releases listed in docs/source/_static/versions.json from their git tags
using the release configuration overlay, and a workflow that runs it when
the manifest (or the overlay, script, or Python dependencies) changes on
main and mirrors the result into versions/ on asf-site. Update the release
instructions accordingly: a release is published by adding it to
versions.json.

Also:
- factor the docs builder setup shared by docs.yaml, docs_pr.yaml and the
  new workflow into .github/actions/setup-docs-builder and run the docs
  jobs on ubuntu-slim
- share a concurrency group between the two workflows that push to
  asf-site
- make the site base path configurable (DATAFUSION_DOCS_BASE_PATH) so a
  fork can test the site, including the version picker, on GitHub Pages

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@github-actions github-actions Bot added documentation Improvements or additions to documentation development-process Related to development process of DataFusion labels Oct 27, 2026
The apache site is served at the root, so the version picker's absolute
paths work as-is. The base path override only mattered for testing on a
fork's GitHub Pages sub-path.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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