bq-analytics-release

Server-driven release management controls update prompts and gating via a centralized Edge Config schema. It coordinates hard blocks, soft nudges, and what's-new prompts across Next.js and React Native clients using a CLI tool to mutate release state.

Coordinating OTA update gating across Expo and Next.js requires a centralized release configuration stored in Vercel Edge Config. A CLI tool seeds and mutates the release state, wiring native and web clients to enforce consistent update actions during incidents.

Vercel Edge Config can control hard blocks and soft nudges for React Native by defining a ReleaseConfig schema with gate and whatsNew properties. The bq-release CLI manages this state, exposing wired client components for native platforms to query and enforce gating.

Bq-analytics release management works with Hono and CLI workflows by providing a bq-release CLI to seed, mutate, and query release state. It wires Hono and Expo clients alongside Next.js to push coordinated release actions during routine updates.

Setting up centralized release configuration involves installing the bq-analytics release package and running a setup script. This defines a ReleaseConfig schema in Edge Config under the key "release", exposing bq-release CLI commands to manage gating and update URLs.

Server-driven release management is needed when coordinating gating, what's-new prompts, and OTA updates across mobile and web platforms. It enables centralized control to push coordinated release actions during incidents or routine updates without redeploying client applications.