Repository navigation
Pin renderer 0.4.0 on the site + auto-bump tool pins on release - #52
Merged
Merged
Conversation
added 2 commits
August 29, 2026 07:43
The Try-it diagram tab renders with @opencoachingformat/renderer; the site was pinned to 0.1.0, so it showed the old renderer (no side/arc routing, old dribble line). Bump to the freshly published 0.4.0. Verified the 0.4.0 browser bundle resolves on jsDelivr and the renderer-playground tests pass.
New receiver workflow: ocf-renderer/ocf-validator fire a repository_dispatch (renderer_released/validator_released) here on publish; this bumps the matching OCF_*_VERSION constant in site/src/lib/ and opens a human-reviewed PR. Same controlled pattern as the spec->validator schema sync — no silent live-site change. Version is semver-validated before it drives the bump.
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
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.
Answers "does the site use the new renderer, or do we need to build auto-update?" — both: fix the acute skew now, and add the automation so it never drifts again.
1. Acute fix — pin renderer to 0.4.0
The Try-it diagram tab renders with
@opencoachingformat/renderer, but the site was pinned to 0.1.0 — so it showed the old renderer (no side/arc routing, old dribble line). BumpedOCF_RENDERER_VERSION→ 0.4.0 (verified the 0.4.0 browser bundle resolves on jsDelivr; renderer-playground tests pass; site builds 35 pages).2. Structural fix — auto-bump on tool release
New receiver workflow
sync-tool-version.yml: when ocf-renderer or ocf-validator publishes, it fires arepository_dispatch(renderer_released/validator_released) here; this workflow bumps the matchingOCF_*_VERSIONconstant insite/src/lib/and opens a human-reviewed PR (never auto-merged). Same controlled pattern as the spec→validator schema sync. The version is semver-validated before it drives the bump.Paired sender PRs add the dispatch to each tool's release workflow:
ci/dispatch-site-on-releaseci/dispatch-site-on-releaseOne-time setup you'll need
The senders require an
OCF_SITE_DISPATCH_TOKENsecret in ocf-renderer and ocf-validator — a token withcontents:write+pull-requests:writeonopencoachingformat/spec. Without it the dispatch step is skipped (releases still succeed), so the automation is inert until the secret is set. (Same shape as the existingOCF_VALIDATOR_DISPATCH_TOKENused by the spec→validator sync.)Leaving merges to you. Suggested order: this PR first (so the receiver exists), then the two sender PRs.
🤖 Generated with Claude Code