I have now finished 3 plugins, and really enjoy the API. A big pain point though has been in updating testers with newer builds since it requires manual steps. For some users its confusing, for some users they just don’t have the time for doing the updates.
- Developer can define in manifest.json a “beta” release
- User can for an installed plugin opt-in to getting the beta release over the live release. (Some kind of toggle to enable beta release usage)
The manifest could appear as:
… other details
If Obsidian finds a beta release upon a check for updates, and the user has enabled using betas for this plugin then Obsidian would update to the beta release. Of course if the user turns beta off, or if there is no beta parameter in manifest.json, the normal release is used for updating.
This would reduce many challenges of properly testing a plugin before updates go out.
One additional bonus would be if a user manually installs a plugin before a plugins release, that it could be updated as well if the manifest has the beta parameter.
Thank you for considering this request. I believe it can lead to better testing and user experiences from plugins in Obsidian.
Consider this my “October” contribution to the community