Ship an update
Release a new version of a plugin that's already on freqlab.co, try a beta first, and deal with a broken version.
1. Make the change and build itLink to this section
Fix or change the plugin, build it locally and check it, then start a cloud build with your signing credentials.
2. Release the new versionLink to this section
Click Distribute on the finished build, then Add to Existing Product and pick the product. In Distro:
- Check the Version is higher than the last one (Distro suggests the next).
- Write Release notes: Collectors see them, so say what changed.
- Save it, then click Publish on its row.
Everyone who owns the product is told about the new version, and gets it as the latest. The new release must still be signed, notarized and pass the Freqlab Standard. See Releases and versions.
Try a beta firstLink to this section
Check Pre-release when you make the release. Owners can pick it from the version list, but the stable version stays what they get by default, and nobody is notified. When it's ready, release the same changes as a new stable version.
If a version is brokenLink to this section
| You want to | Use |
|---|---|
| Stop anyone downloading a broken version | Yank |
| Stop offering an old version, but let owners keep it | Retire |
Then ship the fix as a new version. See Retire, yank or unpublish a release.
Tell peopleLink to this section
On the bug reports it fixes, set Status to Fixed and add Fixed in version, so the people who reported them are told. A community post reaches your followers too.