v1.1.0 - Targeting, rollback fallback, explainable rollouts

v1.1.0 · Targeting, rollback fallback, explainable rollouts

Serving grows up: choose WHICH devices get a release, know exactly what happens to devices on a pulled build, and ask the system why any device gets any version.

Added

• Label targeting per release (tier=canary), fail-closed with fall-through; l.* params on /u/, inline labels on decisions
• Rollback fallback: stranded devices are served the newest published release below as a downgrade (allowDowngrade), with stranded counts and fallback preview before you commit
• "Why this update?" decision trace + per-device Next-check line - the same walk production serves
• Engineering blog at /blog with three launch posts
• Manage serving from CI: PATCH /api/v1/releases (rollout, pause, rollback, targeting)

Changed

• Rollout % and targeting edit freely until the first offer, then only move forward
• Releases tab redesigned: data table, channel filters, serving side panel