Skip to content

CI: verify five press locales and actual rsync staging layout before manual VPS publish - #122

Merged
appdevelopsk merged 4 commits into
mainfrom
ci/validate-press-manifest-rsync-staging-20261113
Nov 13, 2026
Merged

appdevelopsk merged 4 commits into
mainfrom
ci/validate-press-manifest-rsync-staging-20261113

Conversation

@appdevelopsk

Copy link
Copy Markdown
Owner

The missing release test

We proved that all 5 international press pages are HTTP 404 on the actual appdevelopsk.com VPS, despite existing in source and the manual rsync allowlist. The existing "Public App Discovery and SEO QA" was passing, but it did not execute test_preflight_app_discovery.py or test_press_kit.py, and did not trigger on press/** changes.

Changes

  • Include press/**, existing press/SEO preflight sources and their regression tests in BOTH pull_request and push path filters.
  • Actually run the already existing source-truth preflight tests + 5 locale press kit tests in native CI.
  • Add 3 new offline rsync integration tests that parse the current explicit release manifest and run the exact flags -rlcvR --itemize-changes into a disposable temporary www directory (never /var/www/html or a network host), prove every listed published file is byte-identical and in the intended nested path, and prove --dry-run transfers zero bytes.
  • Explicitly verify all five press locale files, catalog, BrainBurst source, no unreviewed privacy-policy spillover and manual opt-in release semantics.

Safety / Validation

  • Read back GitHub branch: only 2 scoped files, 0 commits behind main, 3 new release layout tests, 2 workflow path scopes include press changes.
  • This can now catch any bad release manifest layout or previously unexecuted press preflight before asking an owner to deploy.
  • No VPS, GitHub Pages, social, indexing, GA4 or store write is performed. The CI stages files only under isolated temp directories. Source tests are not a substitute for actual public HTTP 200.

Gate

Require Public App Discovery and SEO QA to pass natively; investigate any newly surfaced preflight bugs before merging. The 5 live 404 routes still need a manually authorized publish to VPS on main with mode=apply and a follow-up live smoke.

@appdevelopsk
appdevelopsk merged commit 9202e43 into main Nov 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant