v0 beta output quality issues and missing publish option

v0
, ,
1

Can’t be the only one whos got constant issue witht he new BETA?

It barely follows a prompt - the output quality os horrific.

I am trying to publish a project, but can’t it options PULL REQUEST, but no PUBLISH ?

I am halfway through a big client system - I have logged support calls and 6 days later had no reply!!???

6

I hear you. The recent v0 beta update replaced the “Publish” button with a GitHub-integrated workflow. Here’s how to publish now:

  1. Click the Git section in the sidebar to connect to GitHub
  2. Create a repository if you haven’t already
  3. Use “Open PR” to publish via pull request

Not seeing publish/PR options? Try generating new code with a prompt, duplicating your chat from settings, or clicking on a versioned message.

For quality issues, the beta is still being refined. Being more specific with prompts and breaking complex requests into smaller steps can help. You can also export as .zip and reimport if a chat gets stuck.

Happy to help walk you through the GitHub setup if you’d like! :folded_hands: Though, if you are seeing issues right now, they may be related to the git incident happening right now.

These docs may help:

1 Like
7

I am really worried - we use this daily and have multiple client projects that i fear we wont deliver based on the BETA - if we can’t OPT out of BETA can someone jump on a zoom for 20 mins to talk through as this could be business closing for us.

8

Subject: Feedback on Beta Deployment Strategy and Production Stability

Hi Pauline,

I’m reaching out to share some critical feedback regarding the current development cycle (I assume Ary is still leading as PM?).

While it’s exciting to see v0 evolving so rapidly, the current approach of replacing stable, reliable functionality with Beta-quality features is causing significant friction. As a senior developer, I have to emphasize that forced migrations to Beta features aren’t aligned with professional environment standards.

A few key observations:

  • Standard Practice: Major paid services typically offer an opt-in for Beta testing rather than a forced rollout.

  • Visibility: Because web environments update silently, we often only discover breaking changes when workflows fail.

  • Recommendation: Could the team move significant Beta changes to a separate, optional playground? This allows for community Q/A without jeopardizing production-dependent projects.

On a side note, I’ve noticed the Design Preview is currently down while waiting on fixes, and there’s a bug where importing projects with a /public folder fails to save. I’ll report the latter formally.

thanks

1 Like