Michael Naumov428 downloadsNotifies you about new app, beta and installer releases — not plugin updates — even when auto-update is disabled. It never installs anything.
Turning off Obsidian's automatic updates also turns off its checking, so from then on nothing tells you a release happened — and the installer version, which carries the Electron that gates several Obsidian features, is never checked at all. This plugin watches all three release streams — the app, the insider (Catalyst) build and the installer — reports what is behind in the status bar, and announces each new version exactly once with a link to its changelog. It never installs anything.
The documentation is a demo vault. Every feature has a note that explains what it does and why you would want it, with buttons that run a real check, read what this machine is actually running, and forget which versions you have already been told about — so you see the plugin working rather than read a description of it.
Start reading here — it is plain markdown, so it works on GitHub with nothing installed.
A copy of the vault ships with every release. You can access it via any of the following:
App Update Notifier: Open demo vault command.app-update-notifier-demo-vault.zip from the Releases. It unzips into a single app-update-notifier-demo-vault-<version> folder.demo-vault/ in this repository.Obsidian's version is three separate answers that move independently, and this plugin reports each one.
obsidian.asar bundle Obsidian loads, and the only piece automatic updates replace. Read from desktop-releases.json, the same file Obsidian's own updater reads. On Android, from the newest release that shipped an .apk.GitHub release, which is the normal case for a Catalyst build, still resolves its changelog from Obsidian's changelog feed.28.2.3, the floor Obsidian itself checks, with the download link built the same way Obsidian's own recommendation builds it.Settings → General → Check for updates names the route that replaces the app bundle alone and leaves the installer where it is. It is a path rather than a button on purpose — Obsidian's own button is wired to an internal updater a plugin could only press by matching translated text in the DOM. On mobile there is one route instead, Update Obsidian: there is no installer to replace, and that settings path is the desktop About tab.Settings → General; on mobile, where there is no such tab and no toggle, the insider Discord channels a Catalyst license opens.Check for updates now command, for when you would rather not wait for the next scheduled check.Checks run once at startup and then hourly, matching Obsidian's own updater; the interval is configurable, and 0 leaves only the command. A check makes four requests, one of which reaches GitHub's API — so an hourly check uses one of its sixty per hour. A failed check is silent and keeps the last answer it had, rather than reporting "up to date" when it means "could not tell".
| Plugin | Features | How App Update Notifier differs |
|---|---|---|
Plugin Update Tracker |
Community-plugin update tracking and risk assessment | Complementary updates: Obsidian app, Catalyst and installer releases only |
Update Radar |
Plugin/theme update checks; release notes; abandoned-addon flags | Complementary updates: Obsidian releases rather than add-ons |
Last searched for similar plugins on 2026-10-26.
The plugin is available in the official Community Plugins repository.
To install the latest beta release of this plugin (regardless if it is available in the official Community Plugins repository or not), follow these steps:
Add plugin button once and wait a few seconds for the plugin to install.By default, debug messages for this plugin (id: app-update-notifier) are hidden.
If you need to enable them refer to the documentation.
All notable changes to this project will be documented in the CHANGELOG.
Contributions are welcome — see CONTRIBUTING to get set up.
Open issues through the issue forms, not as blank issues.
To report a bug from inside Obsidian, run the App Update Notifier: Report a bug command. It opens the bug form with the plugin version, the Obsidian version and your operating system already filled in.
Filing from the CLI or the API (gh issue create --body, or an AI agent filing for you) skips the form, and gh issue create --template cannot load an issue form. In that case, open the matching form in .github/ISSUE_TEMPLATE/, copy every field as a ### <label> heading in the form's order, and fill in each one. Always state the plugin version, the Obsidian version and your operating system.