ci(versions): fan out org-changed dispatch to displayxr-website#399
Merged
Conversation
Phase 2 of the website org-sync. After any versions.json bump commits, nudge displayxr-website to re-pull org data so displayxr.org reflects a release within ~1 min instead of waiting for the website's daily cron. - versions-bump.yml (sibling releases: shell/leia/mcp/demos) and build-windows.yml BumpVersionsJsonOnTag (runtime self-bump) each gain a peter-evans/repository-dispatch@v3 step firing event-type org-changed, guarded by the same did-we-bump condition as the commit step. - continue-on-error + runs after push/mirror: a website hiccup can never fail a real version bump. - displayxr-website added to the publish-bot App token repositories list in both jobs. - Documented the fan-out in versions-json-autobump.md. Website side (scripts/sync-org.mjs + sync-org.yml) already on displayxr-website main. Design: displayxr-website/docs/org-sync.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
dfattal
force-pushed
the
feat/website-org-changed-dispatch
branch
from
6f021fb to
e234662
Compare
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.
Phase 2 of the website org-sync system (full design:
displayxr-website/docs/org-sync.md).What
After any
versions.jsonbump commits, fire arepository_dispatch(org-changed) at displayxr-website so the site re-pulls org data (versions, demo cards, repo list) within ~1 min instead of waiting for its daily cron. The website'ssync-org.ymlregenerates and direct-commits the refresh to its ownmain(it does not open a PR), so this needs no org-wide "Actions may create PRs" policy.Added to both bump paths:
versions-bump.yml— sibling releases (shell / leia / mcp / demos)build-windows.yml→BumpVersionsJsonOnTag— runtime self-bump on tagEach new step:
peter-evans/repository-dispatch@v3, guarded by the same "did we actually bump" condition as the commit step;continue-on-error: true, so a website hiccup can never fail a real version bump;{field, tag, source_repo}for log context (the website ignores the payload and regenerates wholesale).displayxr-websiteadded to the publish-bot App tokenrepositories:list in both jobs. Fan-out documented indocs/specs/runtime/versions-json-autobump.md.Prereqs
displayxr-publish-botApp must be installed on displayxr-website with contents write (org-wide install → already covered).sync-org.ymllistens fororg-changed— already on itsmain.Not exercised until next release
Workflow-only; the dispatch first fires on the next component/runtime release. The website's daily cron is the backstop meanwhile.
🤖 Generated with Claude Code