⌘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
Amy Egan I checked the logs and see a rate limit that expired at the expected time, but nothing currently active. What happens when you redeploy now?
Rogeliocarrascoquiroz 9562 Hi Amy, I redeployed and the new deployment completed successfully. The build-rate-limit is no longer active and deployments are working again. Thank you for checking the logs and confirming the expiration. Best, Rogelio
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.
Amy Egan Hey @nab-admin-2547, are you still getting this error?
Haydarakca Same failure here on 16 Sep 2026: "Failed to create GitHub issue: Bad credentials" on every submit at bots.fyi/new-bot, all fields filled. The same error was fixed manually in June (thread 42165). Could a maintainer refresh the credential, or process this submission directly? Bot Name: GEFTBot Operator: GEFT (https://geft.ai) What it does: search crawler for AI agents; one passive discovery crawl per site, public pages only, obeys robots.txt, not used for AI training. Full description: https://geft.ai/bot User-Agent: GEFTBot/1.0 (+https://geft.ai/bot) Documentation URL: https://geft.ai/bot Verification: Web Bot Auth (RFC 9421, Ed25519). Signature-Agent "https://geft.ai"; signed key directory https://geft.ai/.well-known/http-message-signatures-directory; keyid fuFiadwHtGEjSaIQ37ap_ESPrPkrtCp-Xiogiin-Rqk. No published IP ranges; the signature is the identity. Contact: hello@geft.ai
Nicolas Seems to be a reoccurrence of an issue that already happened a few months ago https://community.vercel.com/t/https-bots-fyi-submission-form-is-broken/42165#post_1 @amyegan any chance you could have a look at this?
PumaPower hello? Anyone out there?
Nickykalliongis 2334 Same issue here. No idea what's going on. I've seen this before, but it always came back, so I thought they were just in the middle of a glitch. Now there's no way to see a previous version unless you revert. So, say I want to go back to a previous version. When I click on it, it asks me to revert before I can see it in read-only view?
