Fix star history chart with sealed-token embed - #29
Merged
Conversation
GitHub restricted the stargazers API (June 2026) to repo admins and collaborators, which broke the anonymous api.star-history.com/svg embed. Swap in star-history's official sealed-token embed: the chart endpoint now carries an encrypted token that can read this repo's stars, with dark/light variants via <picture>. Same sealed token as vessel (covers both repos); verified HTTP 200 on all theme variants before embedding.
2 tasks
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
1 participant
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.
What
Follow-up to #28: GitHub restricted the stargazers API (June 2026) to repo admins and collaborators, which broke the anonymous
api.star-history.com/svgchart embedded in the README.Swaps in star-history's official sealed-token embed:
<picture>Testing
🤖 Generated with ZCode