
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 also use GitHub's email privacy option and haven't run into this problem. Are you sure the metadata is configured correctly? Commits just need to be seen as belonging to your GitHub account if you've already connected it to Vercel
tallneil Not sure - it's possible something wasn't configured correctly, but I decided to disable email privacy in github, and that solved the problem.
Amy Egan glad you found a workaround! lmk if you decide to turn it back on and need help with configuration
Amy Egan It sounds like a metadata issue. Make sure the use info on the commits matches your GitHub account info https://community.vercel.com/t/preview-deployments-stuck-in-unknown-blocked-state-before-build-starts/47000#post_3
Yolanda Update — the issue persists, and I've ruled out several possible causes: Confirmed the latest commit (1cffac8) reached GitHub successfully on main (git log --oneline origin/main confirms it). Fully disconnected and reconnected the Git repository integration in Project Settings → Git (wingroupinversiones/plataforma-bim → plataforma-bim-49hl) — reconnection succeeded ("Connected just now"), all events (deployment_status, repository_dispatch) are enabled. Pushed a fresh empty test commit (git commit --allow-empty -m "trigger deploy test") specifically to trigger a new deployment after reconnecting. Result: no new deployment appears at all in the Deployments list — not Building, not Error, not even a failed attempt. It's as if the push event never reaches Vercel. Ruled out billing/account issues: no payment problems, no restrictions visible under Account → Billing or Account → Overview. The GitHub App installation for Vercel shows the repository correctly authorized under "Repository access." This has now been going on for over 24 hours across multiple commits. Since I'm on the Hobby plan I don't have access to a support ticket — has anyone on staff seen this specific pattern (repo connected + authorized, but zero deployment activity on push)? Happy to provide the project ID or any other diagnostic info that would help.
Amy Egan Metadata mismatch is by far the most common reason for what you're describing. Your email address for local commits needs to match your GitHub account. > You can use `git config user.email` to check it and `git config --global user.email <your-email-address-here>` to update it if needed. Please give that a try if you're still having issues with your commits
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/domains/troubleshooting
Amy Egan If your domain is eligible, you can renew it by following these steps: vercel.com/docs/domains/working-with-domains/renew-a-domain#manual-renewal Keep in mind that third party domains can only be renewed through their current registrar.
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/domains/troubleshooting
Oyaminstitute 8152 It needs vercel human