---
slug: branch-merge-requires-production-write
published: 2026-11-16
change_type: breaking-change
affected_products:
  - Dev Workflows
  - Platform
page: https://supabase.com/changelog/branch-merge-requires-production-write
---

# Merging a branch now requires Production Branches read-write

## What changed

Since November 12, 2026, merging a branch into your main project needs a scoped personal access token with **Production Branches: Read-write**. A token that only has **Development Branches: Read-write** gets a permission error when it calls [Merge a branch](https://supabase.com/docs/reference/api/v1-merge-a-branch) or the MCP `merge_branch` tool.

Creating, pushing, resetting, and deleting preview branches with a development-only token works as before.

## Why we made this change

A merge applies a branch's changes to your production project. Before this change, a token meant only for development branches could still write to production through a merge. Requiring production access closes that gap. A token you give to CI or an AI agent for preview work can no longer write to production.

## Who is affected

You're affected if you merge branches with a scoped personal access token that has Development Branches read-write but not Production Branches read-write. Classic personal access tokens are not affected.

## What happens if you take no action

Merges made with a development-only token fail with a permission error. Your projects, branches, and data stay the same.

## Migration steps

1. Create a new token in [Account > Access Tokens](https://supabase.com/dashboard/account/tokens) with Production Branches read-write. You can't change the permissions of an existing token.
2. Use the new token for the merge step in your CI or scripts.
3. Keep your development-only token for everything else, such as creating and resetting preview branches.

## Rollout timeline

| Date       | Milestone                                        | User action                                      |
| ---------- | ------------------------------------------------ | ------------------------------------------------ |
| 2026-11-12 | Merge requires Production Branches read-write    | Use a token with Production Branches read-write  |

We plan to add a separate Merge permission later, so a token can merge without full production write access.
