Create and edit releases

A release combines a visible version, translated release notes, and one or two platform targets. Each target has its own build number, update mode, and publishing state. You can prepare both platforms together and publish them separately.

Create a draftCopy Anchor Link

You need an app with at least one platform configured.

1. Open Apps, choose your app, and open Releases.
2. Select New release. If the list is empty, Create release opens the same editor.
3. Enter a Visible version, such as 1.4.0 or Summer Release. This is the label people see, not the value used to decide whether an update is newer.
4. Write the Shared changelog (Markdown) for the app's default locale. You can leave the notes unfinished when saving a draft, but publishing requires non-empty shared notes in that locale.
5. Under Platform targets, enable iOS target, Android target, or both. Only platforms configured on the app appear here.
6. Enter the native Build number and choose an Update mode for each enabled target. See update modes before choosing Required.
7. Select Save draft.

The editor returns to Releases, where the release appears as Draft. Saving a new release does not publish either platform.

Add other languages and platform-specific notes with the localization guide. When the release is ready, follow Publish or unpublish a release.

Choose version labels and build numbersCopy Anchor Link

• Visible version is required, must be unique within the app, and can contain up to 50 characters.
• Build number must be a positive whole number. It must match the native build you intend to publish, not the visible version label.
• A build number can appear only once per app and platform. iOS and Android can use different numbers, or the same number independently.
• Use increasing build numbers for newer native builds. VibeUpdate treats the highest published build number on a platform as the latest update, regardless of the version label or the order in which you publish.

Drafts and releases in Recently deleted still reserve their version labels and build numbers. If saving reports that a version or build already exists, check both lists before changing the values. Do not invent a different build number just to clear the error.

Edit a releaseCopy Anchor Link

Changes to a published target take effect when you save. There is no separate review draft for edits to a live release.

1. Open the release's version label in Releases.
2. Update the notes, translations, version label, or target settings.
3. Select Save changes.
4. Check the release in the list, then reopen it to review the saved values.

Existing targets keep their publishing state while you edit. A platform added to an existing release starts as a draft, even if the other platform is already published.

Changing a published target from Optional or Persistent to Required opens Save required mode?. Confirming Save changes applies the required mode to that live target. Review its build number first.

Changing the build number of an already published Required target can also change the minimum supported build. It does not ask you to publish again. Prefer a new release when announcing a different native build.

Remove a platform targetCopy Anchor Link

Turning off a target and saving removes that target from the release, including its publication history. You must leave at least one target enabled. Adding a removed platform again creates a draft target.

To take a target offline while keeping its settings and history, use Unpublish instead.

Delete a releaseCopy Anchor Link

Deletion removes the release from update checks and the public changelog.

• A release that has never had a published target is removed permanently.
• A release with a previously published target moves to Recently deleted and can be restored for 30 days. Unpublishing that target first does not remove its publication history.
• Removing platform targets in the editor does remove their history. Do not remove previously published targets as a way to prepare a release for deletion if you need the restore window.

To delete:

1. Open the release from Releases.
2. Select Delete release.
3. Review the confirmation and select Delete release again.

The release disappears from the active list. A restorable release appears under Recently deleted, with its permanent removal date.

Restore a deleted releaseCopy Anchor Link

Restoring keeps the targets' previous states. A target that was published when you deleted the release becomes available again without another publish step. Check that this is what you want before restoring, especially for Required targets.

1. Open the app's Releases tab.
2. Under Recently deleted, find the release.
3. Select Restore before its restore window expires.
4. Check its status in the active release list.

A permanently deleted draft cannot be restored. If the app itself is deleted, restore the app before managing its releases.