Skip to content

Rebuild smartloop.ai when a release is published - #288

Merged
mehfuzh merged 1 commit into
mainfrom
ci/dispatch-website-on-release
Nov 6, 2026
Merged

mehfuzh merged 1 commit into
mainfrom
ci/dispatch-website-on-release

Conversation

@mehfuzh

@mehfuzh mehfuzh commented Nov 6, 2026 •

Copy link
Copy Markdown
Member

After publish-release promotes the draft to published, send a release-published repository_dispatch to smartloop-ai/smartloop.ai. Its deploy-pages.yml already listens for that event and rebuilds the site with the latest release baked in, so the version shown on smartloop.ai updates right away instead of at the next daily cron. Today the site shows v1.0.69 while 1.0.70 is out.

Setup required: add a repo secret WEBSITE_DISPATCH_TOKEN: a fine-grained PAT scoped to smartloop-ai/smartloop.ai with Contents: Read and write. GITHUB_TOKEN can't dispatch to another repo. Until the secret is set, the step logs a warning and skips. A failed dispatch also only warns, because the release is already live by then.

🤖 Generated with Claude Code

The site bakes the latest published release into its build and listens for a
release-published repository_dispatch, but nothing sent one, so the version on
smartloop.ai lagged until the daily rebuild. Dispatch it right after the
publish step, using a WEBSITE_DISPATCH_TOKEN PAT (GITHUB_TOKEN can't reach
another repo). A missing token or failed dispatch only warns.
@mehfuzh
mehfuzh merged commit 6c01c14 into main Nov 6, 2026
2 checks passed
@mehfuzh
mehfuzh deleted the ci/dispatch-website-on-release branch November 6, 2026 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant