05a4194159
- Add `release_channel` to Settings (Rust + TypeScript) - Add channel selector in Settings panel (alpha/beta/stable) - Pass `release_channel` as PostHog person property on identify - Add `isFeatureEnabled()` helper: alpha always true, beta/stable use PostHog flags with hardcoded fallback defaults - Update `useFeatureFlag` to delegate to PostHog-backed evaluation (localStorage overrides still work for dev/QA) - Create ADR-0042 (supersedes ADR-0017) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.2 KiB
2.2 KiB
type, id, title, status, date, supersedes
| type | id | title | status | date | supersedes |
|---|---|---|---|---|---|
| ADR | 0042 | PostHog-based release channels and feature flags | active | 2026-04-03 | 0017 |
Context
ADR-0017 introduced canary/stable update channels with localStorage-based feature flags. This worked for local development but lacked remote flag management — promoting a feature from beta to stable required a code change and rebuild.
Decision
Replace localStorage feature flags with PostHog-based feature flags, evaluated per release channel (alpha/beta/stable). The release channel is a user-selectable setting; PostHog flag rules determine which features are visible for each channel.
- Alpha: all features always enabled (no PostHog lookup needed, works offline)
- Beta: sees features where the PostHog flag targets
release_channel = beta - Stable (default): sees features where the PostHog flag targets
release_channel = stable - Promotion = flipping a PostHog flag on the dashboard. Zero code changes, zero rebuilds.
isFeatureEnabled(flagKey)intelemetry.tsis the single evaluation point.- localStorage overrides (
ff_<name>) still work for dev/QA testing (checked first). - Offline: PostHog caches flags in localStorage; alpha always works; first-launch-no-network falls back to hardcoded defaults.
Options considered
- Option A: Keep localStorage-only flags (ADR-0017) — no server dependency, but no remote management.
- Option B (chosen): PostHog feature flags — we already use PostHog for analytics, so no new dependency. Remote flag management, per-channel targeting, gradual rollouts via PostHog dashboard.
- Option C: Dedicated feature flag service (LaunchDarkly, Unleash) — more powerful but adds a new vendor dependency.
Consequences
release_channeladded to Settings (persisted via Tauri backend, not vault).useTelemetrypassesrelease_channelas a PostHog person property on identify.isFeatureEnabled()checks channel → PostHog → hardcoded defaults.useFeatureFlaghook updated to delegate toisFeatureEnabled(after localStorage override check).- ADR-0017 is superseded — the canary update channel remains, but feature gating moves from localStorage to PostHog.