/repos/ethereum/go-ethereum/releases missing the latest release

[jonathanudd]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

API

Body

Hello I'm not sure if this is the right place to report this but I thought I would give it a shot at least.

This basically explains the issue

• /repos/ethereum/go-ethereum/releases does not include v1.17.4
• /repos/ethereum/go-ethereum/releases/latest returns v1.17.4
• /repos/ethereum/go-ethereum/releases/tags/v1.17.4 returns v1.17.4
• The web release page exists: https://github.com/ethereum/go-ethereum/releases/tag/v1.17.4
• But it's missing from the list of releases https://github.com/ethereum/go-ethereum/releases

I have only seen this for this specific repository so far.
But I assume this is not a issue that can be solved by the maintainers of that repository which is why I created a post here.

[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. ⭐

[selamet]

This is a known class of GitHub behavior rather than a go-ethereum problem.

The /releases/latest and /releases/tags/{tag} endpoints do a direct lookup of a single release record, so they'll always find v1.17.4 as long as the release object exists. The /releases list endpoint and the web Releases page, however, are served from a separate listing/index — which also has no guaranteed sort order (it's effectively ordered by created_at, i.e. the tag's commit date, not the publish date).

When a release object exists but isn't correctly indexed into that listing — which can happen when a release is created against a tag that already existed, or via automation — you get exactly this symptom: reachable directly, but absent from the list and the web page.

Since v1.17.4 is missing from both the list API and the web page (not just out of order), this looks like a sync/indexing issue rather than sorting or pagination.

Two things worth trying first, both maintainer-side:

• Open the v1.17.4 release, click Edit, then Update release without changing anything. This forces GitHub's backend to re-sync the release, and it usually reappears in both the list API and the Releases page.
• Double-check there isn't a second/conflicting tag v1.17.4 pointing at a different commit.

If neither helps, it's worth raising with GitHub Support, since at that point the listing index has to be refreshed on their end — that part isn't something repo maintainers can force.