Skip to content

Verify docs.libresign.coop refresh after release docs deploy #104

Description

@vitormattos

Context

PR #103 updated the LibreSign release documentation to the current ownership model.

Validated

  • main/developer_manual/release-process.rst describes LibreCodeCoop/release-tool and LibreCodeCoop/.github correctly.
  • manual.rst and configuration.rst are also corrected.
  • Deploy Sphinx Docs run 35950662046 completed successfully for merge commit a8e42b8e72a21cd3cb8d387ce6872a649800c043.
  • gh-pages commit 58eed721bf70e276eab677984656714cb91ca92e contains the corrected generated HTML.
  • gh-pages/CNAME is docs.libresign.coop.
  • current repository/code searches contain no LibreCodeCoop/github-workflows references in the documentation source.

Remaining verification

External web search still returns a crawl from several days before #103, so search results can display the previous release-process content. That stale crawl is not evidence that the current GitHub Pages origin is stale.

The current execution environment cannot perform an uncached live-origin HTTP/DNS check of docs.libresign.coop. Verify the custom domain in a browser (or with an uncached HTTP request) and close this issue once the rendered release-process page matches the current gh-pages content.

This is a publication/search-refresh verification item, not an active dependency on LibreCodeCoop/github-workflows.

Activity

vitormattos commented on Sep 24, 2026

@vitormattos
MemberAuthor

Clarification after deeper verification: GitHub-side publication artifacts are current. The gh-pages branch generated by run 35950662046 contains the corrected release-process, manual, and configuration HTML with no LibreCodeCoop/github-workflows ownership references. The stale public text observed through web search/open came from a crawler snapshot several days old, not a confirmed live-origin fetch. A direct network fetch is unavailable from this execution environment.

Therefore this issue should be treated as a verification item for the custom domain/search cache, not evidence that the current gh-pages deployment itself is wrong. The repository source and generated Pages branch are clean.

changed the title [-]Published docs site serves stale content despite successful gh-pages deploy[/-] [+]Verify docs.libresign.coop refresh after release docs deploy[/+] on Sep 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions