Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Chat clients that add connectors by URL cannot send an Authorization header, so /mcp-open injects a branch-scoped key server-side and forwards to the plugin's /api/mcp. No key ships in this repo.
The i18n proxy matcher rewrites every top-level path that is not api/admin/_next/_vercel into the locale catch-all, so /mcp-open never reached its route handler. /api/mcp-open is excluded from the proxy, and the static segment takes precedence over Payload's /api/[...slug].
NEXT_PUBLIC_SERVER_URL is now branch-scoped, so the MCP tool output and admin links point at this sandbox instead of the shared production demo.
The running deployment started answering 28P01 (password authentication failed for neondb_owner) a few minutes after the previous rebuild, taking the admin, the public site and the MCP endpoint down with it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Holds open a preview deployment of
apps/cmsso a prospect can log in and edit content while they evaluate the CMS against another platform. They asked for a login they could actually try, not a walkthrough.Do not merge, and do not push code here. There is no code diff from
mainon purpose - they should see stock Ideal CMS, not a work in progress. The single file in the diff isapps/cms/SANDBOX.md, which exists so the branch explains itself and so Vercel cannot skip the build for having no changes under the project root.This repo is public, so neither the branch nor this description says which prospect it is for. The mapping and the login live in the deal record.
Why a PR at all
The open PR is what keeps the preview deployment alive, and the Neon integration gives that deployment its own database branch copied from the parent. They can create, publish and delete as much as they like without touching the shared demo data.
Known limits of the sandbox
Vercel crons run on production deployments only, so the hourly
/api/scheduled-publish/runjob does not fire here. A scheduled publish can be set up and inspected, but nothing executes it until that endpoint is called.Retiring it
Close the PR and delete the branch - the preview deployment and the Neon branch go with it.
Do not delete the Neon branch for this branch
The preview's database is a Neon branch the Vercel integration created for
sandbox-c. It looks like an orphan next to themaindatabase, and it is not: a prospect is logging into it right now.Deleting it (2026-08-06) took the admin, the public site and
/api/mcpto 500 with28P01 password authentication failed for neondb_owner, and nothing re-provisions until the next deployment. The redeploy then builds a fresh copy of the parent, so everything comes back looking healthy while the accounts and API keys created for the evaluation are gone - a client-facing login that silently no longer exists.If it does get deleted: redeploy this branch, then re-run the restore script named in the deal record. Do not create a new branch - the preview hostname is derived from the branch name and is hard-coded in material the prospect already has.