fix(ci): Seal the star history token at runtime - #330
Merged
Conversation
The daily Star History job failed with HTTP 400. The chart endpoint only accepts a GitHub token via `sealed_token`, encrypted for the key that star-history.com publishes in its frontend bundle; `token` and `access_token` are ignored. The stored secret was not in that format, so upstream rejected it before decryption and the request fell through to star-history's shared token pool, which is currently exhausted. Seal the token per run instead of storing a pre-sealed blob, so the secret stays a plain, rotatable GitHub token and an upstream key rotation only needs SEALING_PUBLIC_KEY updated. The workflow logged a bare `HTTP 400`, discarding the response body that explained the failure. Include the upstream reason in the error, and stop retrying 400 and 401, which are token problems that retries cannot fix.
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.
No description provided.