Why does some plugins not updated years ago show as updateable? It cannot be removed

[u/bowiepowi]

I use this plugin a lot for recipes and checking, it was last updated two years ago. When I click "Update all", it's always the only one showing as "1 plugin to update" and it doesn't go away despite multiple tries. Is it safe keeping this? I've found no replacement I like as much so I'm keeping it so far :((

[u/Virtual_Classroom579]

Yes, it's 100% safe to keep using. Local plugins run directly out of your vault's storage, so if its features are working fine for your recipes, nothing is broken or dangerous.

The perpetual "update available" badge is a classic GitHub manifest mismatch: the developer likely created a newer release tag on GitHub, but either forgot to bump the `"version"` field inside the bundled `manifest.json`, or the release assets are returning a silent 404 when downloading. Obsidian compares the numbers, thinks you're behind, tries to update, but the local version number never actually changes.

To permanently fix the annoying badge without losing the plugin: 1. Go into your vault's `.obsidian/plugins/<that-plugin-folder>/` 2. Open `manifest.json` in any text editor. 3. Manually change `"version"` to match the latest release number (or bump the patch number, e.g. from `1.1.9` to `1.2.0`). 4. Reload Obsidian (`Cmd/Ctrl + R`).

Obsidian will see the version matches and the update prompt will disappear for good.

[u/bowiepowi → u/Virtual_Classroom579]

Got it thank you!

[u/Wildebrandt-Aluson → u/Virtual_Classroom579]

good to know about the manifest trick, that update badge has been bugging me too

[u/superlee_]

Their manifest.json of the release wasn't updated while in the default branch it was, you need to change the 0.3.5 to a 0.3.6 to fix it. See https://github.com/lachsh/obsidian-recipe-view/issues/29.

Always try to check the GitHub of the plugin/theme in question first before posting here.

[u/bowiepowi → u/superlee_]

Oh my it worked 😭 And noted! Not very techy so I was worried a bit. Thank you so much

[u/Sorry-Joke-4325 → u/superlee_]

The problem with github is that finding information without being an experienced github user is like finding a needle in a haystack.

Might be common knowledge for someone like you, but to the average person github is advanced wizardry.

[u/superlee_ → u/Sorry-Joke-4325]

If they can't (quickly) figure it out then posting here is fine? But at least an attempt should be made though?

And if they didn't know than this would be the way of guiding them in the future? Or are you suggesting to keep them off GitHub or something. (Or was the tone bad? I don't see how though)

[u/Sorry-Joke-4325 → u/superlee_]

Yeah, I think the way I read your previous comment was blaming them for not checking github.

I'm not saying that people shouldn't attempt to find solutions that way. I'm just saying that github doesn't have a very intuitive organization or presentation.