fix(rss): derive feed lastBuildDate from item content dates, not _meta

Follow-up to v2.9.19: deriving lastBuildDate from _meta.last_updated only moved
the drift one level — that analysis timestamp is itself bumped on every publish
even when the ranked content is unchanged, so feed.xml kept differing between
develop and master. Use the freshest item's content date instead (the items only
change when the ranking actually changes). Verified: deterministic across reruns,
and the develop and master digests both yield 2026-06-18, so feed.xml is now
byte-identical across branches — the drift is fully eliminated.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Nubenetes Bot
2026-06-20 12:46:52 +02:00
parent 4d25baee03
commit 01c514b07b
2 changed files with 20 additions and 21 deletions

View File

@@ -5,7 +5,7 @@
<link>https://nubenetes.com/</link>
<description>AI-curated top picks from the Cloud Native &amp; Kubernetes ecosystem</description>
<language>en</language>
<lastBuildDate>Sat, 20 Jun 2026 12:42:56 +0200</lastBuildDate>
<lastBuildDate>Thu, 18 Jun 2026 00:00:00 -0000</lastBuildDate>
<atom:link href="https://nubenetes.com/feed.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Kubecost 🌟</title>