Skip to content

Publish whenever the live page is older, not only for main's head - #103

Merged
github-actions[bot] merged 1 commit into
mainfrom
claude/project-thread-jbqzew
Nov 15, 2026
Merged

github-actions[bot] merged 1 commit into
mainfrom
claude/project-thread-jbqzew

Conversation

@afflom

@afflom afflom commented Nov 15, 2026

Copy link
Copy Markdown
Owner

Since #89, a main run published only if its commit was still main's head. When merges arrive faster than a run finishes, every run finds main has moved on and none of them publishes. Five main runs passed their gates between #93 (live since 04:58Z) and #102 (06:25Z), and none of them published.

tools/pages/newer.sh asks a different question: does the live page (the latest successful github-pages deployment) already hold this commit? The build job uses the answer to decide whether to publish. The publish job, which runs one at a time in pages-publish, asks again just before it deploys, so an older run never replaces a newer page. I checked it against the real repo: main's head and an older commit both give go=true, and a commit the live page already holds gives go=false.


Generated by Claude Code

Since #89 a main run published only if its commit was still main's head.
When merges come faster than a run, every run finds main moved on and none
publishes: nothing deployed from #93 at 04:58Z through #102 at 06:25Z
although five runs passed their gates. tools/pages/newer.sh instead asks
whether the live page already holds this commit. The build job asks it to
decide whether to publish, and the publish job, one at a time, asks again
before it deploys, so an older run never replaces a newer page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3LuNYtPDBa4FbSEQUZ
@github-actions
github-actions Bot enabled auto-merge November 15, 2026 06:30
@github-actions
github-actions Bot merged commit 83d079d into main Nov 15, 2026
7 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

Live: this change is on the published page, as main 83d079ddd8f9a3c2b0bce781cfab3c21b0053ef1.

The publish job opened the published page in a fresh Chromium and its live checks passed (PG-01, PD-01, PD-02): https://github.com/afflom/me/actions/runs/43687588120

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.

2 participants