Git pushes to main don't trigger any deployment (Hobby plan)
Project: estas-bien-claude (Hobby plan)
Connected repo: albertoanibalmari-ship-it/estas-bien-claude on GitHub
Production domain: estas-bien-claude.vercel.app
The problem
Pushes to main stop triggering any new deployment — not a successful one, not a failed one, not even a "skipped" one. The Deployments list (checked with the "All Projects" filter too, not just this project) simply shows nothing after a certain point.
Last deployment that actually worked: ~2026-07-31 17:21 (-03:00), which roughly lines up with commit 8a1674c (2026-07-31 14:18:52 -03:00) or 09cf107 (2026-07-30 19:24:32 -03:00).
Three separate test commits pushed to main since then, none of which triggered anything:
| SHA | Timestamp (-03:00) | Author email |
|---|---|---|
eb77328 | 2026-08-02 03:36:57 | albertoanibalmari@gmail.com |
6d72025 | 2026-08-02 04:50:28 | albertoanibalmari@gmail.com |
3ecb071 | 2026-08-02 05:23:30 | albertoanibalmari@gmail.com |
What I've already ruled out
- Project-level Git connection (Settings → Git): repo shows correctly connected, including after a full Disconnect → Connect cycle done specifically to rule this out.
deployment_statusandrepository_dispatchevent toggles are enabled. - Account-level GitHub connection (Account Settings → Authentication): found this was stale — showed "Last used Apr 16" (~4 months old). Disconnected and reconnected; now shows "Last used just now." Pushed commit
3ecb071after this reconnection specifically to test it — still nothing. - GitHub App installation (checked on the GitHub side, Settings → Installations): correct permissions (Read+Write on code, deployments, commit statuses, checks, pull requests, repository hooks, workflows; Read on actions/metadata), repository access set to "All repositories" (not "Only select repositories"), not suspended.
- Domains: single domain (
estas-bien-claude.vercel.app), "Valid Configuration," assigned to Production. Only one project with this name on the account — no duplicate/stale project silently owning the domain. - Ignored Build Step (Settings → Build and Deployment): set to "Automatic" (default) — shouldn't skip a genuinely new commit SHA.
- Deployment Protection: only "Vercel Authentication" (Standard Protection, Require Log In) is on. As I understand it, this gates viewing deployments, not whether a build gets triggered.
- Commit author email: verified it matches a real, presumably-verified email on the connected GitHub account (
albertoanibalmari@gmail.com, accountalbertoanibalmari-ship-it) — a support agent suggested this as a possible cause, but it didn't turn out to be it, or reconnecting didn't fix it either way.
What I need
At this point I've exhausted everything visible/actionable from the dashboard and from the GitHub side. Has anyone run into silent deploy-trigger failures like this before — webhook/event delivery issue on Vercel's side that wouldn't show up in any of the above? Any pointers on what else to check, or whether this needs a human to look at delivery logs on Vercel's end, would be appreciated.