Repository navigation
Keep the observation date and the social card in step with the data - #94
Merged
Merged
Conversation
The home plate's "last observation" date was already read from the data at build time; it now comes from one helper, lastObservationDate, with a unit test. The social card (public/og.png) draws the same matrix and now prints the same date, and the deploy workflow regenerates it from the deployed data before every build, so a merged observation PR updates both without a manual `pnpm generate:brand`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0175HbpkBt7vwjM2ctcU5Xam
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.
Requested by Jan · project thread
What was going on
The home plate's "last observation" date was already read from
data/observations/at build time, and every merge to main redeploys. The live page shows 2026-11-03 today, which matches the newest observation (the scanner run merged in #90). A2026-10-22you may have seen is the fifth row of the Latest observations list (one row per server and requirement), or a cached copy of the page from before #90's deploy.What did not follow the data was the social card (
public/og.png): it draws the matrix but was only refreshed by hand withpnpm generate:brand.Changes
lastObservationDate(data)insrc/lib/atlas.tsis the one source of the date, used by the home plate and the social card, with a unit test.39 servers × 23 requirements · last observation 2026-11-03, like the home plate.deploy.ymlrestores Playwright's Chromium (same cache key asci.yml) and runspnpm generate:brandbeforepnpm build, so the published card always matches the deployed data with no extra commit. A unit test pins that order; every new step keeps the stale-commit gate.public/og.pngregenerated;docs/development.mdnotes the deploy step.Not covered: the README pictures under
docs/assets/readme/still needpnpm generate:readmeby hand, since GitHub serves them from the repository rather than the deployed site.Checks
pnpm checkpasses locally.Generated by Claude Code