Skip to content

Verify live Pages content anonymously after publishing - #3

Merged
valzargaming merged 1 commit into
mainfrom
docs-pages-anonymous-readback-20261020
Oct 20, 2026
Merged

valzargaming merged 1 commit into
mainfrom
docs-pages-anonymous-readback-20261020

Conversation

@valzargaming

Copy link
Copy Markdown
Member

Adds anonymous HTTPS verification after the existing Pages deployment: require HTTP 200 and compare seven key pages/resources byte-for-byte with the exact published artifact. Curl ignores local configuration, receives no credentials/cookies, and uses bounded timeouts/retries. Permissions and deployment targets are unchanged.

PR #2 deployed successfully in run39462732706, but this operator's network resets connections to the public Pages hostname. The runner-based check supplies independent anonymous readback and keeps that verification on future deployments. Actionlint and whitespace checks pass; focused independent review and normal CI precede merge. No Google credentials, uploader gates, paid services or protection changes are involved.

@valzargaming
valzargaming merged commit 3496f1c into main Oct 20, 2026
11 of 12 checks 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