Publish revisable RST documentation through R2 - #11
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The documentation Worker can now select a documentation revision independently of the Gecode release version. Gecode 6.4.0 serves the verified RST manual from revision
20260905-rst2; later text and HTML corrections can use a fresh revision while keeping the same public version and latest URLs.This adds immutable R2 revision prefixes and preview URLs, conditional direct uploads, complete object/hash verification, revision-aware caching and deployment smoke checks, and the website's HTML manual entry link. The historical archives remain available. The release-support coordinator consumes these publication helpers for both new releases and documentation-only updates.
The 6.4.0 seed and Worker selection are already live. This PR records that deployed Worker configuration and the publication machinery on the website branch; it does not create a Gecode release.
Validation: full website quality gate passed, including 16 publication-tool tests and 34 documentation Worker tests. All 5,382 seed objects match the manifest; production HTTP checks passed across explicit revisions, versioned URLs, both latest aliases, search assets, PDF ranges, canonical headers, and 404s. Browser search and result navigation passed at the mounted preview and latest URLs, including a narrow viewport.