Publish or unpublish a release

Publish a target when its native build is ready for your users. Publishing in VibeUpdate makes release notes and update information available. It does not upload or release the app in either store.

Before publishingCopy Anchor Link

Check the saved release and the app's Settings:

• The target's Build number matches the native build available to users.
• iOS has a Bundle ID and an App Store URL. Android has a Package name and a Google Play URL.
• Store links use HTTPS. The iOS link must use apps.apple.com, and the Android link must use play.google.com.
• The release includes non-empty Shared changelog (Markdown) in the app's Default locale. A platform override alone does not meet this requirement.
• Each target has the intended Update mode. Review update modes if you are unsure.

Store availability is something you must check. A saved store link does not establish that the new native build is available there.

If Public page enabled is on, publishing also adds the target to the public changelog. There is no separate publish action for the public page.

Publish a platformCopy Anchor Link

Publishing Required can block older builds through the app's update prompt. The highest published required build for that platform sets the minimum supported build. A newer Optional release does not remove a minimum set by an older required target.

1. Open your app's Releases tab.
2. Find the saved release. Open its version label first if you need to review or edit the content, then save and return to the list.
3. Select Publish ios or Publish android next to that release.
4. For a Required target, review the confirmation and select the same publish action again.
5. Check the release badge and the target's action button.

A published target's button changes to Unpublish ios or Unpublish android. The badge summarizes all targets included in that release:

Repeat the publish action for the other platform when it is ready. Publishing one does not publish the other.

Unpublish a platformCopy Anchor Link

Unpublishing removes that target from update decisions and public release history. Other published targets remain available. If you unpublish the latest build, an earlier published build may become the latest available update. Unpublishing a required target can lower or remove the minimum supported build.

1. Open the app's Releases tab.
2. Select Unpublish ios or Unpublish android beside the release.
3. Check that the button changes back to the corresponding Publish action and that the badge reflects the remaining targets.

Unpublishing takes effect without a confirmation dialog. It does not delete the release or change an app already installed on someone's device.

You can publish the target again after checking the prerequisites. Republishing keeps that target's original publication date. It does not reset the date to today or necessarily move the release to the top of the public changelog.

To hide only the website while keeping published updates available in the app, turn off Public page enabled instead. See public changelog visibility.

If publishing failsCopy Anchor Link

A store link or identifier is missingCopy Anchor Link

Open Settings, fill in the platform's identifier and store URL, and select Save changes. Then return to Releases and try the publish action again.

You cannot remove a platform's identifier or store link while that platform has active published targets. Replacing these values also affects existing releases, so check them before saving.

"default locale shared changelog is required"Copy Anchor Link

Check Settings > Default locale. Open the release and select the matching locale button. If it is missing, enter that exact locale in Translation locale and select Add locale. Write shared notes, select Save changes, and publish from the list.

Notes only in iOS override (optional) or Android override (optional) are not enough. See localization.

The new target is not the latest updateCopy Anchor Link

Check the published build numbers for that platform. The highest build number wins, not the most recently published release or the largest-looking Visible version. A device already on that build or a newer one has no pending update.