ci: daily refresh of committed release/star data - #33
Merged
Conversation
The deployed site already refreshes both files at build time via the deploy cron; this keeps the committed fallbacks fresh too, so local builds show current numbers and an API failure during deploy falls back to at-most-a-day-old data. Pushes with the default GITHUB_TOKEN, which does not retrigger workflows — the 06:17 UTC deploy cron 30 minutes later picks the commit up. Skips the commit entirely when nothing changed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Follow-up to #32. The deployed site already bakes fresh
releases.json/stars.jsonat build time (deploy cron, 06:17 UTC daily); this workflow keeps the committed fallbacks fresh too, so local builds show current numbers and an API hiccup during deploy falls back to at-most-a-day-old data instead of whenever-someone-last-ran-the-script.workflow_dispatch.scripts/refresh-releases.pyunchanged; commits and pushes tomainonly when the files actually changed, asgithub-actions[bot].GITHUB_TOKEN, which by design does not retrigger workflows — no double deploy; the deploy cron picks the commit up 30 minutes later.permissions: {}at top level withcontents: writescoped to the job,persist-credentials: falsewith an explicit token on the push.Ponytail review: one noted shrink (single-job
defaultsblock, −3 lines) — kept for symmetry with deploy.yml.🤖 Generated with Claude Code