Releases Atom feed does not reflect Releases page content

[garciat]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Body

(Expected content) Releases page: https://github.com/dotnet/fsharp/releases

(Actual content) Releases feed: https://github.com/dotnet/fsharp/releases.atom

Which looks more like this: https://github.com/dotnet/fsharp/tags.atom

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[hoangperry]

Reproduced and confirmed — this is a real discrepancy, and it's precise: I pulled both feeds just now, and releases.atom for dotnet/fsharp is entry-for-entry identical to tags.atom (same items, same order, including tags like pre-v4-reset-20260610-1535 that have no release at all), while the actual Releases returned by the API (/repos/dotnet/fsharp/releases) are a completely different set. So the "releases" feed is being generated from tag history, not from release objects — for repos that tag far more often than they publish releases (like fsharp), the feed becomes useless as a release-tracking mechanism.

Workarounds that track actual releases until this is fixed:

1. Watch → Custom → Releases on the repo — the notification path does use real release objects, so you get exactly what the Releases page shows (email/web notifications rather than RSS, but accurate).
2. The REST API (GET /repos/dotnet/fsharp/releases) is the ground truth — trivial to poll from a script or a scheduled Action if you're feeding automation rather than a feed reader.

Worth keeping this discussion focused on the reproducible core when it gets triaged: releases.atom ≡ tags.atom on this repo is a crisp, verifiable claim that makes the bug undeniable.

[thomasfinstad]

This issue generates considerable noise in any feed where the project tags several components per release and gives a very false impression of what is going on with the releases of any project affected.