You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of 2023-10-04, the cursors used by GitHub's GraphQL API when listing a repository's tags simply encode the total number of tags in the repository at the given point, and if a tag is deleted, the final cursor "decreases". Thus, if reponews reports a tag for a tracked repository, and then N tags are deleted from the repository, reponews will not report any more tags for that repository until after N+1 more tags are added, and then it'll only report the most recent one.
The text was updated successfully, but these errors were encountered:
As of 2023-10-04, the cursors used by GitHub's GraphQL API when listing a repository's tags simply encode the total number of tags in the repository at the given point, and if a tag is deleted, the final cursor "decreases". Thus, if reponews reports a tag for a tracked repository, and then N tags are deleted from the repository, reponews will not report any more tags for that repository until after N+1 more tags are added, and then it'll only report the most recent one.
The text was updated successfully, but these errors were encountered: