Перейти к содержимому
Начать проект

Статья

Ring Promoter v1.0.2 — Rings, Orbit and Lanes Side by Side

Technical brief: Orbit Deployer Board, NEW Lanes matrix, Descent stage, ops polish since v1.0.1, and how the promotion protocol stays unchanged

  • 3 мин чтения
На этой странице

Long-form companion to the v1.0.2 blog. Release notes and product context: TenthMatrix Ring Promoter · ringpromoter.com · GitHub v1.0.2.

Ring Promoter v1.0.2 — Rings, Orbit and Lanes

youtu.be/hNU4sWxrDFk · Happy Friday release — 25 September 2026

Thesis. v1.0.2 does not change the promotion protocol — it gives operators two first-class views of the same truth: Orbit for the fleet, Lanes for the environment matrix. Rings remain the ordered pipeline; these UIs make “how far has this build earned?” obvious at a glance.
QA tests failing on a Friday? No worries. Ring Promoter will keep your applications healthy and auto-rollback if a promote lands unhealthy. When QA gates pass, auto-promote continues hop by hop all the way to Acceptance; production still waits for the human / password gate. See also: QA gates technical brief.

1. Ring Promoter v1.0.2 — what shipped

From the official release notes on GitHub and the “CI/CD Orbit and Lanes, side by side” section on ringpromoter.com:

Surface What you get
Orbit Deployer BoardEarth at centre as live users. Promotion rings are orbits — PROD closest in, then ACC, TEST, INT as outer spokes. Newest versions solid; older hollow. Gates and app roster ride alongside.
Lanes (NEW)APP × INT / TEST / ACC / PROD matrix. Same version across rings stretches as one pill. Prod lag is a visible break — no hunting per-app pages.
Descent and stageDescent treats rings as orbits (Lanes fallback). Cinematic Earth stage: more sky, quieter labels, collision-aware leaders.
Ops since v1.0.1In-place ring restart, external QA agent scaffolding, multi-arch images, longer Helm waits for cold pulls, clearer workstation secrets for production password gates.

2. Orbit vs Lanes — when to use which

Orbit beside Lanes

  • Orbit — pause here for the fleet: which apps climbed how far toward prod, with gates visible beside the stage.
  • Lanes — flip here for the matrix: parity across environments, or an obvious split when prod still has to earn the hop.

Both are companions to the walkthrough on ringpromoter.com — not a second source of truth. The control plane still enforces one ring at a time, source health, target health, auto-rollback, and history.

3. The protocol underneath (unchanged)

  1. One ring at a time — promote always targets the next ring; skipping is impossible by design.
  2. Source must prove it — live health on the source gates every hop.
  3. Target must earn it — health with retries after deploy.
  4. Failure undoes itself — unhealthy target rolls back automatically.
  5. Everything is written down — seed, promote, rollback in history per (app, ring).

TenthMatrix product overview: /en/ring-promoter. Prior deep dives: modern CI/CD, QA gates, every release earns production.

4. TenthMatrix angle

On TenthMatrix instances, v1.0.2 makes multi-app release control rooms readable under load: Orbit for situational awareness, Lanes for “is prod behind?”, and the same YAML-onboarded apps, kubectl / GitHub Actions deployers, and production password gates operators already use.

5. Videos

Published by TenthMatrix.

Ещё технические статьи