[PR #1375/a47e20f9 backport][3.36] fix: RSS feeds show stale data for rebuilt packages

[patchback]

This is a backport of PR #1375 as merged into main (a47e20f).

Summary

• Use Max() instead of Min() for the added_at timestamp aggregation so feeds reflect the most recently added file for each (name, version) pair
• Append a #timestamp fragment to the <guid> so RSS readers treat rebuilds as new items, and set isPermaLink="false" accordingly
• Raise UPDATES_LIMIT from 100 to 500 for indexes with large batch promotions

Context

When a package is rebuilt with a different PEP 427 build tag (e.g., pkg-1.0-1-...whl then pkg-1.0-2-...whl), the RSS feed continued to show the original timestamp and guid because iter_releases() used Min("file_added_at"). RSS readers never surfaced the rebuild as a new item because the <guid> was unchanged.

The 100-entry limit in updates.xml was also too small for indexes that receive batch promotions of 100+ packages at once (we've seen promotions of up to 117 packages in a single hour).

Fixes #1374

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 7c319a77-8b38-45b6-baed-0c3114446266

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}