Best Practice for: Beta Plugin becomes "offical" Community Plugin

I have several beta plugins that I update via BRAT. Some of them might get a code review done sometime and become “official”.
Therefore, they will be listed in the Community Plugin List and updated via a different process to my Obsidian installation.


  • Any reason why I should scan list for those plugins and move them from BRAT Install to the Community Install?
  • Any automatic scan that does this?

Thanks in advance

The same reason you might want to move off of any beta software — stability.

I’m also interested in automating this process.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.