docs(runtimes): runtime changelog + periodic update tooling#800
Draft
HayesGordon wants to merge 3 commits into
Draft
docs(runtimes): runtime changelog + periodic update tooling#800HayesGordon wants to merge 3 commits into
HayesGordon wants to merge 3 commits into
Conversation
HayesGordon
marked this pull request as draft
July 17, 2026 17:30
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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.
Adds a runtime changelog at
/runtimes/changelogand the tooling to produce it periodically - covering all 8 Rive runtimes (Apple, Android, Web, React, React Native, Flutter, Unity, Unreal) plus a derived Core runtime section for shared C++ changes. As a bonus, it keeps the docs' install-version snippets from going stale.How it works
The design splits deterministic facts from one AI editorial step:
scripts/runtime-changelog/collect.mjs.claude/skills/runtime-announcementscripts/runtime-changelog/digest.mjsscripts/runtime-changelog/state.jsonVersions, dates, and links are never AI-authored - the agent only writes wording.
--advance-statealso syncsdocs.jsonversion variables (versionApple,versionWeb, …) to each runtime's latest, so wired install snippets never rot.Usage
One command in Claude Code:
/runtime-announcement. It collects releases → drafts the entry → shows you the entry + a preview of the community post → you approve → it records state and bumps docs versions → you reviewgit diffand commit. The community post is saved togenerated/community-post.md(git-ignored) for pasting into Discord/forum. Full runbook inscripts/runtime-changelog/README.md.What's in this PR
collect.mjs,digest.mjs,state.json,README.md, the skilldocs.json: nav entry + auto-synced runtime version variables6.13.0→current, RN default block6.12.0→current)Everything is local and human-reviewed - no commits, pushes, or PRs happen automatically.
Still on the table
changelog.mdx(grouped by date) andchangelog-per-runtime.mdx(grouped by runtime, filterable). Delete the loser + its tempdocs.jsonnav entry before merge.CLAUDE.mdstill saysmintlify- the CLI is nowmint. Separate cleanup.rive-runtimehas no releases yet. When it does, Core can link a specific version.package.jsonif it ever lags.