Publish Your Project

Publish turns a tested Preview into a stable public version. Use it when the Preview matches your intent and you are ready to share the Project outside your workspace.

Publishing does not close the Project. It creates a Project Version from the current Spec and code, while your Project stays open for the next iteration.

When to publish

You are ready to publish when the Preview represents the version you want others to use.

Before publishing, check that:

• The Preview matches the Project Spec and your product intent.
• The main user flows work end to end.
• Required runtime secrets are configured.
• There are no unresolved blockers or Spec conflicts.

Treat Preview as the place to test and refine. Treat Publish as the moment you make a stable version available to others.

What Publish creates

Each Publish creates a Project Version. A Project Version pairs the product definition with the implementation that shipped.

Later edits to the live Project do not rewrite past Project Versions. They become part of the next version when you publish again.

📄Spec snapshot

The frozen product definition for this Project Version.

📦Code snapshot

The exact implementation that was published.

🏷️Project Version

The stable public version created from those two snapshots.

Before you publish

When you publish, Castaly runs a pre-publish check. This check only surfaces blockers that already exist; it does not create new issues at publish time.

Two things can hold publishing:

• An unresolved Build blocked state caused by a Spec conflict.
• A missing required runtime secret, shown as Configuration required.

A missing secret does not block Build or Preview, but it does block Publish. Add the secret in Project Settings, then publish again.

If a Spec conflict blocks publishing, resolve it first in Resolve Spec Conflicts. For the full blocker map, see Resolve Blockers.

What happens during Publish

1. 1

   Castaly checks publish readiness

   Castaly confirms that the Project is ready to publish and shows any blocker that must be resolved first.

2. 2

   A Project Version is created

   Castaly captures the Spec snapshot and code snapshot for this Project Version.

3. 3

   The published version goes live

   The Project Version is published to its public address.

4. 4

   The main button becomes View site

   The primary action switches to View site, so you can open the published version from the workspace.

After you publish

After publishing, you can open or copy the public URL from the top bar. The published version stays stable even as you continue working on the live Project.

🔗Share the published version

Use the published URL when you want others to view the Project.

🧷Keep the version stable

Future edits do not change this Project Version until you publish a new one.

🔁Continue the Project

Refine the Spec, build the next change, test the next Preview, and publish again.

Keep iterating

Publishing creates a stable Project Version, not an endpoint. Your Project remains editable after every publish.

The next iteration follows the same loop:

Spec → Build → Preview → Publish

Each time you publish, Castaly creates a new Project Version from the current Spec and code.

In Home, Projects, and the Project Workspace, a shipped Project appears as Published so you can scan for what is live. See Project States.

Next: Project States maps every status you’ll see along the way.