[pull] master from supabase:master

apps/docs/content/guides/auth/server-side/nextjs.mdx

@@ -264,7 +264,8 @@ export async function updateSession(request: NextRequest) {
   if (
     !user &&
     !request.nextUrl.pathname.startsWith('/login') &&
-    !request.nextUrl.pathname.startsWith('/auth')
+    !request.nextUrl.pathname.startsWith('/auth') &&
+    !request.nextUrl.pathname.startsWith('/error')
   ) {
     // no user, potentially respond by redirecting the user to the login page
     const url = request.nextUrl.clone()

apps/docs/content/guides/deployment/branching/dashboard.mdx

@@ -58,8 +58,6 @@ When reviewing a merge request you may see a notice at the top of the page askin
 There are a few limitations you should be aware of before deciding to use branching without git.
 
 - Custom roles created through the dashboard are not captured on branch creation
-- Only public schema changes are supported right now
-- Extensions are not included in the diff process
 - Branches can only be merged to main; merging between preview branches is not supported
 - If your branch is out of date, you can pull in latest changes from main, but keep in mind that all functions will be overwritten
 - Deleting functions must be done manually on main branch