Repository navigation
CI: verify five press locales and actual rsync staging layout before manual VPS publish - #122
Merged
appdevelopsk merged 4 commits intoNov 13, 2026
Conversation
This was referenced Nov 13, 2026
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
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 missing release test
We proved that all 5 international press pages are HTTP 404 on the actual
appdevelopsk.comVPS, despite existing in source and the manual rsync allowlist. The existing "Public App Discovery and SEO QA" was passing, but it did not executetest_preflight_app_discovery.pyortest_press_kit.py, and did not trigger onpress/**changes.Changes
press/**, existing press/SEO preflight sources and their regression tests in BOTHpull_requestandpushpath filters.-rlcvR --itemize-changesinto a disposable temporarywwwdirectory (never/var/www/htmlor a network host), prove every listed published file is byte-identical and in the intended nested path, and prove--dry-runtransfers zero bytes.Safety / Validation
Gate
Require
Public App Discovery and SEO QAto pass natively; investigate any newly surfaced preflight bugs before merging. The 5 live 404 routes still need a manually authorizedpublish to VPSonmainwithmode=applyand a follow-up live smoke.