Repository navigation
Use stargazerCount instead of restricted stargazers - #54
Merged
Merged
Conversation
GitHub has recently blocked access to the list of stargazers and watchers. This includes the `stargazers` property in GraphQL, which in this case can be replaced with `stargazerCount`. Fortunately, `watchers.totalCount` still works. https://github.blog/changelog/2026-06-30-upcoming-access-restrictions-to-public-api-endpoints-and-ui-views/
Member
|
Looks good, but I can't do the release right now, so I'll leave it here and merge it once I'm able to do the release. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GitHub has recently blocked access to the list of stargazers and watchers. This includes the
stargazersproperty in GraphQL, which in this case can be replaced withstargazerCount. Fortunately,watchers.totalCountstill works.This should fix the errors seen in Express Statusboard.
https://github.blog/changelog/2026-06-30-upcoming-access-restrictions-to-public-api-endpoints-and-ui-views/