Retire, yank or unpublish a release
Stop offering a version, pull a broken one, or take one back to draft, and what each means for the people who own your product.
Each release's actions are on its row in Releases; the info button explains them.
| Action | What happens | Owners |
|---|---|---|
| Retire | Stops offering this version as the download | Can still download it from their library |
| Yank | Withdraws a broken release | Can't download it until you republish it |
| Unpublish | Turns it back into a draft, hidden from everyone | Only possible until anyone owns the product |
| Delete | Removes the release for good (the build files stay with their builds) | Drafts always; any other release only until anyone owns the product |
Once people own the product, its releases can't go back to draft or be deleted: retire one to stop offering it, or yank one that's broken.
While the product is published, the only release with files for a platform can't be retired, unpublished or deleted, since its owners would have nothing to download. Publish a newer build for that platform first, or yank it if it's broken.
RepublishLink to this section
Republish offers a retired or yanked version again. It keeps its original date, so a newer release stays the latest. If you changed its files with Edit, it's dated now and announced as an update, which only the newest version can be: an older version's fix ships as a new version.
Removed by FreqlabLink to this section
If Freqlab takes a release down, it shows Removed by Freqlab. Collectors can't download it, and you can't change it until it's restored. Contact support@freqlab.co to have it reviewed.