Rank, 14 days: 10 on the Vercel sheet
9 people reported
All time, since Aug 15.
First deploy classified Production
“The returned deployment is immediately classified as target: production.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/vercel/issues/9150/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
First deployment recorded as Production despite Preview target. On a new project with no prior deployments, vercel deploy --target preview without --prod returns a deployment with target: production.
Is this your bug?
File my report- Where
- Vercel CLI
- Versions
- 59.0.0 to 64.2.0
- Platforms
- macOS, Windows
- How bad
- Breaks a normal workflow. Some reports say it blocks them completely.
Not quite your bug?
Original reports9, newest first
- First deployment ignores explicit Preview target: supported path without a Production bootstrap?#51312
- First deployment forced to Production despite --target=preview#51252
- First deployment with --target preview was recorded as Production#50903
- First Preview deployment without any Production bootstrap#50848
- First protected Preview without a Production bootstrap#50726
- Vercel MCP deployment target mismatch: staging requested, production created#50570
- First deployment on empty Hobby project is classified as Production even from preview branch#49203
- Feature-branch deployment was classified as Production instead of Preview#47885
- First deployment becomes Production despite Preview intent — safe non-production path?#47794