fix(blog): set post dates to their actual merge times - #340
Merged
Conversation
The blog post `pubDate`s were hand-picked, drifting from when each essay actually landed (e.g. "The Loom You Can Read" read 2026-07-01, a future date). Set each `pubDate` to the merge timestamp of the PR that introduced it, so the listing, the `<time>` element, and the RSS feed reflect reality: a-great-pirate-age #308 2026-06-28T00:28:34Z (unchanged) data-should-work-like-soil #311 2026-06-28T01:23:39Z (unchanged) the-gentlest-furnace #312 2026-06-28T02:27:04Z (unchanged) the-desert-that-feeds-the-forest #321 2026-06-28T21:46:46Z the-right-to-say-no #323 2026-06-28T22:10:50Z the-forest-and-the-field #326 2026-06-28T23:39:38Z the-loom-you-can-read #332 2026-06-29T01:09:07Z Also reorder desert/right-to-say-no to keep the source array newest-first (the runtime sort is by pubDate regardless). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: xNet Test <test@xnet.dev>
Contributor
|
Preview removed for PR #340. |
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.
What
The blog post
pubDates were hand-picked and had drifted from when each essay actually shipped — most visibly "The Loom You Can Read", dated2026-07-01(a future date). This sets each post'spubDateto the merge timestamp of the PR that introduced it, so the listing order, the<time>element, and the RSS<pubDate>all reflect reality.pubDate(merge time)2026-06-28T00:28:34Z(unchanged)2026-06-28T01:23:39Z(unchanged)2026-06-28T02:27:04Z(unchanged)2026-06-28T21:46:46Z2026-06-28T22:10:50Z2026-06-28T23:39:38Z2026-06-29T01:09:07ZThe first three already matched their merge times. Source of truth: each PR's
mergedAt(verified against the merge-commit committer date onmain).Also reordered the desert / right-to-say-no entries so the source array stays newest-first (the runtime sort is by
pubDateregardless).Verification
astro build✓ (107 pages)/blog: cards in correct newest-first order;<time datetime>and RSS<pubDate>carry the exact merge timestamps ✓No changeset (confined to
site/);skip-changelogsince this is a metadata correction, not a user-facing feature.🤖 Generated with Claude Code