/repos/ethereum/go-ethereum/releases missing the latest release · community · Discussion #200014 · GitHub
Skip to content
Discussion options

You must be logged in to vote

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: reac…

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@jonathanudd
Comment options

Answer selected by jonathanudd
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug GitHub or a GitHub feature is not working as intended Apps API and Webhooks Discussions related to GitHub's APIs or Webhooks source:ui Discussions created via Community GitHub templates API Discussions around GitHub API platform and docs
2 participants