v0.6.0

Minor Changes

• 88c3305: Add OpenCode 2.0.27 support while preserving OpenCode 1.17.4+ compatibility. Both server and TUI entrypoints expose the appropriate host hook. V2 uses native integration credentials for the host's active account, account-specific refresh and disconnect, and scoped OAuth cleanup; existing V1 local credentials require a new login on V2. Keep real Zod tool schemas for both hosts, register bundled skills, and port /supabase with browser authorization and onboarding. The connected V2 dialog uses OpenCode's native selection component for plugin-defined Continue/Disconnect actions; advanced account management stays in V2's native /connect integration UI. Add V2 packed-TUI CI coverage and prune V2's npm cache before uploading diagnostics.

  Builds on Rafael Santos's (@rafaelsnv) initial V2 migration in PR #79.

Patch Changes

• e918865: Make the packed-TUI e2e harness compatible with OpenCode V2 (@opencode/cli): register the plugin by writing project .opencode/opencode.json (V2 plugin add is an interactive wizard), use lowercase --log-level debug, and isolate the V2 managed serve --service daemon on its own port. V1 behavior unchanged.
• 0acee2b: Fix the OAuth callback writing tokens to the wrong local auth store (#32). Persist tokens against the per-flow pending auth entry (keyed by state) instead of the singleton callback server's first-call input, so concurrent flows for different directories no longer cross-write each other's store.
• daa6816: Fix V2 OAuth refresh dedup dropping its entry too early and keying on the raw broker URL (#90, #91). Keep a successful refresh cached under the consumed old refresh token until the process ends: the OpenCode host persists the rotated credential only after refresh() resolves, so a second resolve in that window must converge on the cached result instead of re-sending the single-use token (broker 401). Failed refreshes still delete the entry so waiters are released and a retry reaches the broker. Dedup keys now strip the trailing slash with the same normalization makeBrokerRequest() applies, so https://host/broker and https://host/broker/ aliases no longer send the credential twice.
• e549fc1: Refresh vendored Supabase skills from supabase/agent-skills v0.1.9 (commit 544bfc5). Adds scoped personal access token guidance, declarative schema workflow, and a debugging section to the supabase skill; broadens the supabase-postgres-best-practices trigger description; records both skill changelogs. Provenance updated in skills/.upstream.json. Context: #46.

v0.5.1

Patch Changes

• 2af61f4: Pin the published dependency contract (exact @opencode-ai/plugin and open versions, drop unused @opencode-ai/sdk and zod) and make the packed TUI build rewrite host-runtime imports in an import-aware way.

• b58c450: Fix /supabase failing to load on recent OpenCode versions: the published package shipped raw TSX through ./tui, and once the host stopped transforming TSX under node_modules, the import crashed on react/jsx-dev-runtime before the plugin could register.

  Ship the rich /supabase TUI as compiled JavaScript (dist/tui.js) and rewrite @opentui/core, @opentui/solid, and solid-js imports at build time to canonical opentui:runtime-module:* IDs generated by OpenTUI's runtimeModuleIdForSpecifier(). Imports resolve to OpenCode's host-owned runtime modules, so the custom dialog renders without plugin-private OpenTUI/Solid copies (which threw No renderer found from a duplicate renderer context). Those packages are now optional peers and dev dependencies, not production dependencies.

  Ship a self-contained declaration for ./tui so TypeScript consumers can resolve the package without installing host-owned optional peers or enabling skipLibCheck.

v0.5.0

Minor Changes

• 398f393: Remove the supabase_get_project_api_keys tool from the public tool surface.

Patch Changes

• 398f393: Declare OpenTUI and Solid as runtime dependencies so clean package installs can load the TUI export.
• 4a044e3: Broaden the OpenCode Supabase guide skill triggers so Supabase project, key, URL, /supabase, and exact MCP connection prompts load the guide reliably.
• 398f393: Add clean packed-package import smoke coverage for the server and TUI plugin exports.

v0.4.2

Patch Changes

• 53ea5a2: Fix Supabase auth store path resolution for Windows drive-letter, UNC, and extended-length paths so credentials are written to the correct project worktree root instead of mixing separators or falling back unexpectedly.

v0.4.1

Patch Changes

• f71506e: Switch npm publishing to trusted publishing with GitHub OIDC and update repository links for the transferred supabase-community repo.

v0.4.0

Minor Changes

• 3d50f7a: Update default OAuth broker URL and client ID for new Supabase project deployment

v0.3.1

Patch Changes

• 35f3b08: Tighten Supabase MCP onboarding copy to guide users from listing projects into MCP connection.

v0.3.0

Minor Changes

• 691346a: Add Supabase MCP onboarding: plugin-owned opencode-supabase-guide skill, authenticated supabase_open_mcp_setup server tool, updated TUI onboarding message, and README docs.

v0.2.2

Patch Changes

• a5d9160: Persist Supabase onboarding before navigating to newly created chat sessions, preventing the prompt from being dropped when confirming an already-connected account from the home screen.

v0.2.1

Patch Changes

• 3a6ea04: Prevent ambiguous broker refresh errors from clearing saved Supabase auth.
• 6fe8bd6: Recover corrupt Supabase auth store instead of crashing. Invalid or unsupported store files are backed up, reset to a valid notice state, and surfaced through the /supabase dialog and tool errors.