Skip to content

fix(registry): realign vi-federation 'Pages generated' timestamp#55

Merged
drknowhow merged 1 commit into
mainfrom
fix/vi-federation-timestamp-consistency
Jun 19, 2026
Merged

fix(registry): realign vi-federation 'Pages generated' timestamp#55
drknowhow merged 1 commit into
mainfrom
fix/vi-federation-timestamp-consistency

Conversation

@drknowhow

Copy link
Copy Markdown
Owner

Follow-up: main was red on registry pages match a fresh build. vi-federation/index.html carried Pages generated 2026-06-19T10:09:53Z while the index + all 19 other pages say 2026-06-18T09:09:15Z — a stray timestamp from a concurrent partial regen (not from the dead-link PR #54, which did not touch vi-federation). A fresh build pins the timestamp from the index, so vi-federation drifted.

Realigned to the index timestamp; build_registry_pages --check passes. 1-line, content otherwise unchanged.

🤖 Generated with Claude Code

vi-federation/index.html carried Pages generated 2026-06-19T10:09:53Z
while every other registry page and the index say 2026-06-18T09:09:15Z
— a stray timestamp from a concurrent partial regen. A fresh build
pins 'Pages generated' from the index, so vi-federation drifted and
the 'registry pages match a fresh build' CI gate failed on main.
Realigned to the index's timestamp; build_registry_pages --check now
passes. Content otherwise unchanged (1 line).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@drknowhow drknowhow merged commit 2586d0c into main Jun 19, 2026
7 checks passed
@yepgent yepgent deleted the fix/vi-federation-timestamp-consistency branch June 19, 2026 10:18
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