Back to Signal Feed
CodeTracked since May 19, 2026

Add a credential-light local dev bootstrap flow for Superset

Superset now adds a local contributor setup path via `bun setup:local` that enables a fresh clone to boot a local web/API/desktop stack without required third-party credentials, while keeping strict validation for cloud/internal profiles and isolating each worktree’s local DB and desktop state.

bun setup:localSUPERSET_PROFILEdeployment profileslocal profile

What Happened

  • Superset now adds a local contributor setup path via `bun setup:local` that enables a fresh clone to boot a local web/API/desktop stack without required third-party credentials, while keeping strict validation for cloud/internal profiles and isolating each worktree’s local DB and desktop state.
  • Superset now adds a local contributor setup path via `bun setup:local` that enables a fresh clone to boot a local web/API/desktop stack without required third-party credentials, while keeping strict validation for cloud/internal profiles and isolating each worktree’s local DB and desktop state.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Introduces a local-first bootstrap flow that copies local env examples, derives worktree-specific names, starts required local services, applies migrations, and seeds a local admin account, while allowing missing optional integration credentials in `local`/`ci` and preserving strict checks for `cloud`/`internal`.

Why Track This

Why It Matters

Developers can now bring up a local Superset environment from a fresh clone without hunting for OAuth, payment, email, or queue service credentials, which lowers setup friction and makes onboarding and parallel local worktree development faster. The `local` profile now runs with non-blocking optional integration checks and explicit worktree-scoped DB/desktop state, while production and canary behaviors remain strict; operators should watch for accidental environment-profile leakage (especially with `VERCEL` markers), and for cleanup behavior when local worktrees are removed so stale state does not accumulate.

Impact

Developers can now bring up a local Superset environment from a fresh clone without hunting for OAuth, payment, email, or queue service credentials, which lowers setup friction and makes onboarding and parallel local worktree development faster. The `local` profile now runs with non-blocking optional integration checks and explicit worktree-scoped DB/desktop state, while production and canary behaviors remain strict; operators should watch for accidental environment-profile leakage (especially with `VERCEL` markers), and for cleanup behavior when local worktrees are removed so stale state does not accumulate.

What To Watch Next

  • Watch whether bun setup:local becomes a repeated pattern.
  • Track follow-up changes around AI IDE.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: profile_switching_accidentally_forces_wrong_validation_mode, local_worktree_state_not_cleaned_between_checkouts.
Open Topic TimelineOpen Technical EventOpen Original Sourceprofile_switching_accidentally_forces_wrong_validation_mode / local_worktree_state_not_cleaned_between_checkouts / blank_optional_integration_credentials_triggering_edge_case_paths

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

superset-sh/superset PR #4616: feat: local dev without third-party credentials

The PR introduces `bun setup:local` plus local env/profile wiring so local dev can run against Docker Postgres and Electric even when OAuth, Stripe, Resend, QStash, and other optional integration keys are absent.