goalmatic deploy --preview. A Site command creates a preview deployment. An App command creates an immutable private test build and prints its build status.
For a Site, choose a production hostname once in the project’s Domains settings.
Select Use build domain for a free your-name.goalmatic.site address, then
connect it. Domain setup currently happens in the dashboard.
Publish the selected source revision with goalmatic publish. Publishing saves
the production revision; it becomes reachable at the connected hostname. If no
domain is connected, the preview URL still works, but there is no public
production hostname yet.
An App release has separate states. Push the configured preview branch to origin, create a private test build with deploy --preview, review its runtime, then promote the exact tested tree from that preview branch to the configured production branch with:
--test-build-id <build-id> to select one explicitly. The command reads the clean local preview checkout and exact preview head, then asks the server to validate the live host, tree, and baseline at submit time. The server promotes that tree without a merge or new build, then submits the same compiled artifact to Store review. The command does not switch your checkout or silently create a new build. Use --dry-run for a plan only. Use --yes for a non-interactive submit or JSON script.
The tested build’s manifest and the current supported Store listing contract
provide the App’s capabilities, visibility, and listing metadata. Promotion does
not silently make a private App public, change capabilities, or bypass the first
Store review.
If review is required, the App is not live while review is pending. After approval, finish it with:
git push origin preview → goalmatic deploy --preview → review the test runtime → goalmatic publish --from-preview → review when required → goalmatic publish --release-id after approval.
For the current production path, goalmatic publish --test-build-id <build-id> remains available when your clean local checkout already matches the configured production branch and commit.
Read status between stages with goalmatic status --json. After a command returns, verify the exact route, revision, or release ID. A cached response does not prove that production changed.
The new --from-preview and --release-id flags require a CLI release that exposes them. Verify goalmatic --help or inspect the local source before using them with the current npm beta.