⌘K
NextBlock™ CMS Just submitted our application for **NextBlock CMS**! 🚀 NextBlock is an open-source, full-stack CMS framework built natively for **Next.js 16 (App Router + RSC)** and **Supabase (PostgreSQL JSONB)**. We’ve focused on: * **Zero-Config 1-Click Deploy:** Automated Supabase database migrations on build. * **100/100 Lighthouse Defaults:** Tiptap visual editor renders PostgreSQL JSONB directly into React Server Components, eliminating client hydration overhead and HTML sanitization taxes. * **Cortex AI & Native MCP:** Model Context Protocol server support (`/api/mcp`) for deterministic, schema-constrained block synthesis. * **GitHub:** https://github.com/nextblock-cms/nextblock * **Live Sandbox:** https://cms.nextblock.dev Looking forward to the review process and collaborating with the Vercel DX team! 🧱
Axyl1410 Hi! I applied for the Summer 2026 Vercel OSS Program, but I’m not sure whether my application was successfully submitted. I also didn’t receive a confirmation email. Is there any way for applicants to verify whether their application was received, or is there normally no confirmation email after submitting the form? I’d like to avoid submitting a duplicate application if my original submission went through. Thanks!
Amy Egan If you reached the final page that says, "Thank you," then your application was received :) You'll get an email about a week after applications close letting your know whether or not your project was accepted
Proppurity 5334 Update: This issue is still unresolved after 10 days, and the topic currently shows 0 replies. Could a Vercel staff member please check the orphaned deployment directly? Deployment ID: dpl_BuS6bYHCymV12EvxDBRcKtcSMMqD The original project has already been deleted, but the deployment is still serving the old site. I only want the orphaned deployment removed/disabled. Please do not modify my current project or www.purityprop.com. Thank you.
Proppurity 5334 Hi Vercel team, Here is an additional update on my issue. The old URL https://purityprop-ai.vercel.app still serves the previous PurityProp website, even after I deleted the `purityprop-ai` project from my PurityProp account. I ran the following commands using Vercel CLI 59.16.0: `npx vercel project inspect purityprop-ai` Result: `Error: There is no project for "purityprop-ai"` `npx vercel inspect https://purityprop-ai.vercel.app` Result: `Error: Can't find the deployment "purityprop-ai.vercel.app" under the context "purity-prop1"` My alias list and project list are also empty under the currently selected team. Could you please investigate which deployment or hostname association is still serving the old website and remove or detach it? Please preserve my working production URLs: - https://www.purityprop.com - https://purityprop.com - https://purityprop-ai-seven.vercel.app I cannot identify the active deployment from my current account, so I would appreciate your assistance in locating it. Thank you.
Robert Groves Well, the setup that I was previously able to get to work started to error out on September 23rd. All calls using meta/muse-spark-1.1 started failing with: \`Error \[GatewayInternalServerError\]: The web_search tool is not supported when Zero Data Retention is enabled.\` The AI Gateway Settings dashboard shows that Zero Data Retention is not enabled though, so that's strange. I know it can be enabled per call as well, but I'm not doing that either. I have a support ticket open, but if anyone here is using muse spark with its built in search grounding successfully, would love to compare notes.
Robert Groves In case anyone lands here for similar reasons, here's the latest: In the period between September 23rd and October 7th this was broken for currently unconfirmed reasons. It's working again since October 8th. As for the why it broke, I've been back and forth with a helpful Vercel support team member and the latest is: > ...it is on our team's radar. From our initial investigation, it looks like this may have been something that happened as a result of the model provider.
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Thiego Thanks. I reviewed the 404 debugging guide. The common 404 causes listed there do not appear to match this case: - the active Preview deployment exists and is READY - the immutable deployment URL is correct - /login loads successfully - initial _next assets load successfully - build output is healthy - there is no vercel.json - repository configuration does not rewrite or cache /login POST requests - Deployment Protection/OIDC access is working The 404 only occurs after submitting the Next.js Server Action. The POST /login response is returned with: x-vercel-cache: HIT and contains an x-nextjs-deployment-id from an older deployment. The stale Server Action/RSC payload then references build-specific assets from that older deployment, and those asset requests return 404 on the current immutable deployment. So the 404 appears to be a downstream symptom of the stale cached Server Action response, rather than a missing route or deployment-output issue. Could a human from the Edge/Next.js platform team please review the x-vercel-cache: HIT / stale x-nextjs-deployment-id behavior?
