Skip to content
FIRERUN.

The BaaS & deploy-platform newsroom for builders

Subscribe

Supabase

Supabase Branch Merges Now Fail With Development-Only Tokens

CI merge steps that use a development-only token now hit a permission error. Mint a Supabase token with Production Branches read-write for merges.

Hand-drawn editorial illustration for "Supabase Branch Merges Now Fail With Development-Only Tokens"

Supabase now refuses to merge a preview branch into production unless the scoped access token doing it can write to production, so a CI job or agent that merges with a development-only token gets a permission error instead of a deploy. Supabase listed the change as breaking in its Nov. 16 changelog and said it has applied since Nov. 12 (Supabase changelog, Nov. 2026).

What Changed

The rule covers two paths: the Management API’s merge endpoint (POST /v1/branches/{branch_id_or_ref}/merge) and the MCP server’s merge_branch tool. A scoped personal access token now needs the Production Branches: Read-write permission for either one. Supabase’s API reference for the endpoint now lists branching_production_write as the required fine-grained permission.

A token with only Development Branches: Read-write can still create, push, reset and delete preview branches, Supabase said. It just can’t merge.

Supabase said a merge writes a branch’s changes to production, so a development-only token could reach production through it.

Classic personal access tokens are not affected, according to the changelog. If nobody acts, merges with development-only tokens fail, and Supabase said projects, branches and data stay unchanged.

How to Fix It

Supabase’s migration steps:

  1. Create a new token under Account > Access Tokens with Production Branches read-write. Existing tokens can’t have their permissions edited.
  2. Use the new token only for the merge step in CI or scripts.
  3. Keep the development-only token for the rest of the preview-branch work.

The company also said it plans a separate Merge permission, so a token could merge without full production write access.

Who Gets Hit

Scoped tokens are recent. Supabase began rolling them out in alpha on Aug. 10 and made them generally available on Oct. 6, when its MCP server began enforcing their permissions. Teams that gave their agents and pipelines narrow, development-only tokens since then are the ones this change breaks. Anyone still on a classic token sees nothing.

The Take

This is the right fix, and it exposes a hole that should worry anyone who set up least-privilege tokens in the last two months. For weeks after GA, a token labeled for development could reach production through a merge. If an agent held one, the agent could ship.

The fix is also awkward. Until the separate Merge permission arrives, the only way to keep merging from CI is to hand that step a token that can write to production in general. Keep that token in its own secret, wire it into the merge job alone and keep it away from any agent that only needs preview branches. Then check every pipeline that merged since Nov. 12. A merge job that failed and got retried or ignored means production is behind the branch the team thinks shipped.

Stay in the loop

Get new articles in your inbox

We'll only email you when a new article drops. Unsubscribe anytime.