Publishing tries your database changes on a copy first

When you publish an update to a Cloud app that changes its database, Playcode now tries those changes on a copy of your live data first. If they would fail on the real data, the publish stops before anything changes.

• Your live site keeps running. It stays on the previous version, and its data stays exactly as it was.
• You see what went wrong. The publish panel shows the database's error, so the agent can fix the change and publish again.
• Updates without database changes publish as before.

Before, a database change that did not fit the live data could fail halfway through an update and leave later publishes stuck until it was repaired. This covers the database setup Playcode starts every Cloud app with.