index: regen after estate rescan (498 scans)#55
Merged
Conversation
The scans from hypatia run 29843933209 landed on main via PR #54, but the index did not: the publishing workflow split scans and index into two PRs and exited before opening the second one. So index.json still carried last_updated=2026-06-25T17:40:00Z while scans/ had moved to 2026-07-21 — i.e. index-freshness.yml was failing on main. This regenerates it with the repo's own scripts/regen-index.sh against merged main, so the timestamp is the real post-merge scans commit. Touches only index.json, no file under scans/, which keeps regen-index.sh's last_updated derivation stable across the squash merge. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
index.jsonwas left stale on main: PR #54 landed the scans, but the publishing workflow exited before opening its index PR. Regenerated with the repo's ownscripts/regen-index.shagainst merged main.last_updated: 2026-06-25T17:40:00Zlast_updated: 2026-07-21T16:37:34+01:00(= the commit that landed scans/)Touches only
index.json. That matters:regen-index.shderiveslast_updatedfromgit log -1 -- scans/, so an index-only squash leaves that derivation stable, whereas squashing scans+index together would not.