What shipped on OpenVibe.OpenRe
Every change deployed to OpenVibe, newest first. Each line is a commit from the OpenVibers repositories, linked to the change itself. When enough have gathered, or a large feature lands, they are written up as Patch notes on openvibe.blog. JSON: /api/v1/changelog.
2026-09-24
ea87a94The shared update system and one account UI, on the OpenVibe Frame (openvibe-shared 1.11.0, openvibe/frame): the home shows what shipped, /updates is the shared log and the footer links it; the shared navbar handles sign in and out…
4df7677One W3C trace across services (Track O): openvibe-shared v1.7.0 trace.install(app) keeps each request's traceparent and puts it on the calls made while serving it, to loopback and OpenVibe hosts only
f03a2c0Loopback /metrics (Track O): openvibe-shared/metrics on openre-api (request rates and latencies, process metrics, release_info) plus openre_sessions{state} for starting and live ingest sessions
7934bd8CI calls the shared test workflow (Track Q): OpenVibe.Shared test.yml@e8b0caf (install, node --check, npm test, openvibe-contracts-check; ffmpeg where the tests need it) instead of a copy of those steps
40afbddrelease.json names the deployed commit: a release directory (releases/<sha>) has no .git of its own, so the manifest said 0000000; RELEASE_COMMIT, OPENRE_RELEASE or the directory's sha now supply it
f391183Serve the release manifest (Track R, D43): GET /release.json on openre-api (release, contracts, openvibe-shared/sdk/contracts versions) through openvibe-shared release; test in drill-mode.test.js
ef21212Session lineage from Live's canonical resolver (D20): the coordinator asks OpenVibe.Live's /internal/lineage/resolve (live.lineage.resolve, OpenRe's service token) which channel each Live-linked definition belongs to (mirror_to_live or a…
e517ed4SECURITY.md: how to report a vulnerability ([email protected], 7-day reply, scope, supported versions)
2026-09-23
cc70a5aopenvibe-shared v1.5.1, openvibe-contracts v0.33.0
cf90bacopenvibe-shared v1.5.0, openvibe-contracts v0.32.0, openvibe-sdk v0.5.0
c091a09CI: run the shared security workflow (gitleaks secret scan + dependency audit, Track Q)
4339a9eStatus: A2-A6 and C done on production (release e0dc1b46fd99, public bind, Live wired, preflight PASS, drill passed); A4 not needed — 1936 answers from outside
5e86ea7OPENRE_DRILL: restore-drill mode. openre-api serves reads from the restored copy and answers 503 openre.drill_read_only to writes, /play/ and sign-in; /api/ready reports mode drill. The coordinator and every transport worker refuse to be…
e0dc1b4RTMP cutover runbook and tooling. docs/cutover.md covers the whole cutover with owner and agent steps, a check and an undo for each: deploy the newest release, OPENRE_RTMP_BIND=0.0.0.0 through a new worker generation, 1936/tcp at the…
450f87cDocs: STATUS.json and README match production (2026-09-23)
6dc78a5nginx: client address headers only from $remote_addr (realip). X-Forwarded-For was appended to and CF-Connecting-IP passed through from the client, so a request reaching the origin without Cloudflare (DNS-only host or the bare IP) chose…
655b98aopenvibe-contracts v0.16.0 (openre manifest and capabilities released); contracts check is blocking
a2ddd2bReview fixes: output reports only land for the worker that owns the output (a lost worker can no longer stop a released or reassigned output), destination keys scrubbed from ffmpeg errors, logs and events, loopback players cannot keep a…
cc1524brtmp-e2e: no ingest or destination key in any process log
3fa6daaWorkers: keep the RTMP worker up on an uncaught exception once started (node-media-server's own behaviour), kill ffmpeg children when the restream worker exits, hand unstarted outputs of a draining generation back; Live patch: events must…
34dea5eDeploy (systemd units per process, worker generations as template instances, nginx for openre.stream, deploy.sh), .env.example, README with the per-protocol port status and cutover runbook, STATUS alpha, CI, capability and service manifest…
d975045Migration from a Live DB snapshot (new keys only, held/excluded rows recorded, idempotent) with the per-channel cutover checklist; recording, relay, destination and UI tests
7aedddcOpenRe.Stream runtime: stream definitions with hashed ingest keys, sessions with a state machine and leases, transport workers with generations (RTMP ingest on node-media-server, restream on ffmpeg), session coordinator, Media recording…
2026-09-21
d9fef29Charter: OpenRe.Stream as defined in the OpenVibe realignment plan (placeholder, no code yet)