/repos/ethereum/go-ethereum/releases missing the latest release #200014
-
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
This is a known class of GitHub behavior rather than a go-ethereum problem. The 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 Two things worth trying first, both maintainer-side:
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. |
Beta Was this translation helpful? Give feedback.

This is a known class of GitHub behavior rather than a go-ethereum problem.
The
/releases/latestand/releases/tags/{tag}endpoints do a direct lookup of a single release record, so they'll always findv1.17.4as long as the release object exists. The/releaseslist 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 bycreated_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: reac…