GitHub Pages deployment history

The Scarp documentation website deploys automatically after changes to main are merged and the GitHub Pages workflow completes successfully. It publishes the English pages at /scarp-docs/ and the Hindi pages at /scarp-docs/hi/ in one deployment.

The count above is fetched from the public GitHub Actions API and represents successful runs of the pages.yml workflow, not the number of commits, branches, or distinct website versions. If GitHub rate limits the request, use the linked workflow history instead. Each meaningful merged change triggers a deployment; there is no need to run a workflow merely to increase this number.

Where to inspect deployments

• GitHub Pages workflow history — view the build and deployment jobs and their status.
• Repository deployments — GitHub's deployment records, if available.
• Live documentation and Hindi documentation — verify published content.

Production builds and the independent compiler conformance check are handled by the Documentation CI workflow. A passing build does not imply that a compiler feature has shipped; the feature status remains tied to the compiler release.

Automated post-deployment check

After the Pages deployment, the smoke job fetches 12 live English/Hindi URLs, including nested clean URLs, the current alpha.6 installer guides, tutorials, release notes and community pages. It checks HTTP 200, document language, canonical and reciprocal hreflang tags, and public JavaScript/CSS bundles. The entire generated sitemap, not just a handful of URLs, must match every English/Hindi Markdown source page exactly once. Missing, duplicate, wrong-host or wrong-base sitemap URLs make the workflow fail. The same completeness check runs on the built static artifact before deployment. Temporary propagation delays are retried; persistent failures mark the workflow unsuccessful. The same assertions have offline regression tests in Documentation CI.

This HTTP smoke test is not a substitute for browser QA. Before closing the post-deployment QA issue, manually verify mobile sidebar behavior, keyboard navigation, Ctrl/⌘+K local search, theme contrast, copy buttons and browser console errors.