Skip to content

Fix the documentation root redirect - #102

Merged
Marenz merged 1 commit into
frequenz-floss:v0.x.xfrom
Marenz:fix/docs-site-default-redirect
Oct 5, 2026
Merged

Marenz merged 1 commit into
frequenz-floss:v0.x.xfrom
Marenz:fix/docs-site-default-redirect

Conversation

@Marenz

@Marenz Marenz commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Make the documentation root redirect to latest after publication. The advertised root currently returns 404 while versioned docs work.

The publish-docs CI job never calls `mike set-default`, so the
gh-pages branch has no root index.html and
https://frequenz-floss.github.io/frequenz-client-marketmetering-python/
returns a plain GitHub Pages 404. The README and pyproject.toml
Documentation link both point at that root URL.

Add a `mike set-default latest` call right after `mike deploy` in
the publish-docs job, mirroring what the test-docs job already does
for its ephemeral build. Using the `latest` alias (rather than the
version computed for the current CI run) keeps the site default tied
to the latest stable release, so pushes that only publish a -dev
build never make a dev snapshot the default.

Signed-off-by: Mathias L. Baumann <mathias.baumann@frequenz.com>
@Marenz
Marenz requested a review from a team as a code owner October 5, 2026 15:02
@Marenz
Marenz requested review from llucax and removed request for a team October 5, 2026 15:02
@github-actions github-actions Bot added the part:tooling Affects the development tooling (CI, deployment, dependency management, etc.) label Oct 5, 2026
@Marenz
Marenz merged commit dd03a37 into frequenz-floss:v0.x.x Oct 5, 2026
9 checks passed
Comment thread .github/workflows/ci.yaml
# Make sure the site root (gh-pages index.html) redirects to the
# `latest` alias. Without this, the documentation website root URL
# 404s, as `mike deploy` alone never creates that redirect.
python -I "$(command -v mike)" set-default latest

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This need to be done only once, no need to put it in the CI, you just missed some setup steps. Recommend reverting so you don't diverge from the repo-config templates unnecessarily, it can break future migration scripts affecting this part.

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.

Right, it was already applied once on gh-pages. Reverted in #103.

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

Labels

part:tooling Affects the development tooling (CI, deployment, dependency management, etc.)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants