Why are plugins delisted if an update doesn’t pass the automated review?

Devs: Plugins & API
, ,
1

Instead of removing the plugin from the store, why not keep the older version that passed the review?

2

I believe this was changed 4 days ago (2026-07-15) to match the behavior you’re expecting.

3

Hmm, it seems like the plugin is on the store but I guess it doesn’t become searchable? I think it might be an issue with obsidian, because I also published a new plugin and couldn’t find it. I had to install it via the website.

4

If you can provide a link to the relevant plugin(s) I can take a look.

5

Here’s my plugin, that recently failed review. I’ll avoid shipping the small fix for now. It looks like it got removed from the store, if you search on the site or in the app. Maybe it takes time to delist.

6

I probably missed the window, it appears that your plugin is passing the automated review and is installable, and has been since August 5. Is it not installable on your end?

image
image761×383 31.4 KB

7

I actually confirmed that the plugin is removed from the store completely instead of keeping the latest version. I am just requesting an adjustment where if the previous versions of a plugin passes and the latest updated is rejected to simply keep the previous version of the plugin and add it to a list of plugins to avoid automatically checking for.

Once new thing I discovered, though, is that it seems that the store checks for new updates on at least a weekly update automatically. I could be wrong, though, as maybe I requested a review and totally forgot, similar to turning off the stove or locking a door being routine tasks your brain skips writing memories for.

8

I was either misinformed or I misunderstood that they don’t delist plugins, you are correct with how it currently works, a plugin will be delisted if an update fails.

The team is aware and are working towards fixing this, unknown ETA.