reference_changelog_pages - EyevinnOSC/community GitHub Wiki
name: reference-changelog-pages description: community.wiki has two changelog pages (Platform-Changelog.md, Recent-Platform-Changes.md) that should get an entry alongside any service page update for a user-facing platform change metadata: type: reference
The community wiki maintains two separate changelog-style pages in addition to service/guide pages:
-
Platform-Changelog.md— dated (daily) entries grouped by repo + version, e.g.### osaas-app v7.94.0. Explicitly indexed by the OSC architect RAG system so users can ask "what was recently deployed?". Newest date goes at the top, right after the intro paragraph and---. -
Recent-Platform-Changes.md— a rolling changelog organized by feature area (## My Apps,## Databases,## Parameter Stores,## Custom Domains, etc.) rather than by date-first. Each bullet is- YYYY-MM-DD: <description>. See [repo#PR](url).New entries go at the top of their feature-area section.
When documenting a merged PR that changes user-facing platform behavior (not just a new service page), add an entry to both of these in addition to updating the relevant Service:-*.md / User-Guide:-*.md / Developer-Guide:-*.md page. If the change is to a repo without semver releases (e.g. Eyevinn/web-runner, a container image repo with no meaningful version tags — checked via gh api repos/Eyevinn/web-runner/tags), cite the repo name and PR link instead of inventing a version number.
See project_web_runner_node_upgrade for the first case this was applied to (2026-08-04, web-runner#50).