Skip to content

fix(production-check): hosted first-run probes - #67

Draft
drozhzhin-n-e wants to merge 1 commit into
mainfrom
cursor/production-check-hosted-02e1
Draft

fix(production-check): hosted first-run probes#67
drozhzhin-n-e wants to merge 1 commit into
mainfrom
cursor/production-check-hosted-02e1

Conversation

@drozhzhin-n-e

Copy link
Copy Markdown
Contributor

Aligns npm run production:check with a real hosted first-run (schema + public-v1, no Stripe yet).

Changes

  • Validate anon key via organizations probe (hosted HEAD /rest/v1/ can 401 with a valid key)
  • Treat app-level 404 from public-v1 as deployed (not gateway “function missing”)
  • Billing Edge Functions are optional warnings until Stripe is intentionally deployed

Verified against hosted

  • Migrations 00000035 applied
  • public-v1 ACTIVE
  • production:check exit 0 (warnings only: no seed, billing not deployed)
Open in Web Open in Cursor 

Treat billing Edge Functions as optional, distinguish gateway 404 from
app-level 404 for public-v1, and validate the anon key via a real table
probe instead of HEAD /rest/v1/.

Co-authored-by: Nikita Drozhzhin <drozhzhin-n-e@users.noreply.github.com>
@vercel

vercel Bot commented Jul 17, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
saas-starter Ready Ready Preview, Comment Jul 17, 2026 8:42am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants