Skip to content
Merulan

Publish an App

Check an installed App and its release evidence, publish the intended version, then read back what viewers receive.

Publish an App from its installation in the intended Workspace. Use its Product's publication procedure to prepare a version, then inspect the installation and release evidence. A deployed draft is not yet the version viewers receive.

Publish the checked version against the observed current version. The request must identify the same installation and pass the release checks. If another builder published first, read the current version and decide whether your version should follow it.

After publication, open the App as the intended viewer. The bootstrap read identifies the version served to that viewer; also check that its data reads are permitted. A successful publish changes the served App version, but it does not grant new rights to underlying Workspace data.

To change a published version later, inspect the current installation again. A revert checks that the earlier version's dependencies and settings still fit; it is not an unchecked pointer change.