Build and preserve release-specific documentation bundles - #10
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Vizard needs to ship the same complete manual that appears in its online release archive. This adds a release builder that produces one static bundle with an app-version label, offline search, and a hashed manifest. Deployment copies previously built release bundles unchanged and generates an online version chooser, so future styling changes do not alter old manuals.
The latest five app-wiki updates are carried into the public manual before it becomes the maintained source. Current documentation still deploys from main.
Validation: release preview built with 98 HTML pages; archive-preservation and checksum-failure tests pass; 10,594 generated links/assets resolve. Native-server Chromium checks passed for offline search, nested reloads, desktop/mobile layout, and identical presentation across two origins. No historical releases are fabricated. Production Pages deployment will be checked after merge.
Merge this before the companion app integration, which fetches this repository's main branch for new builds.