Update Radar

approvedunreviewed

by siulved54

Checks your installed community add-ons for updates in the background, shows release notes and flags abandoned ones. A successor to the unmaintained Update Tracker.

↓ 205 downloadsUpdated 7d agoMIT

Update Radar

Checks your installed community plugins for updates in the background, shows what changed, and tells you which plugins look abandoned. A successor to Plugin Update Tracker, which has not had a release in over a year.

The Plugin updates view listing four plugins with installed and available versions, release notes opened for one of them, and a plugin health section with a "No release in 2+ years" flag

Formerly "Plugin Update Checker" and, briefly, "Community Update Checker"; renamed because the directory does not allow the word "plugin" in a name and the second name was already taken by an earlier submission.

Obsidian only looks for plugin updates when you open Settings → Community plugins → Check for updates. This plugin does it for you, every few hours, and puts the answer in the status bar.

What you get

  • Updates in the status bar. "3 plugin updates", hidden when there are none. Click it to open the list.
  • A list of what changed. Each row shows the installed version, the new one, and, when you open Release notes, the notes from the plugin's GitHub release, rendered as Markdown.
  • Update one or all. The same installer Obsidian uses; enabled plugins are reloaded afterwards.
  • Ignore this version. Skips exactly that version; the next release shows up again. Stop ignoring brings it back.
  • Go back to an earlier version. An update broke something? Right-click a plugin in the list, use the history button on an update row, open Install an earlier version at the bottom of the list, or run the command of the same name. You see the plugin's releases (up to 30) with version, date and the start of the notes; the installed one is marked, and a version that needs a newer Obsidian than yours is greyed out. Update Radar then stops offering the version you went back from.
  • Compatibility. An update that needs a newer Obsidian than yours is listed apart, with the version it needs, and is never offered.
  • Plugin health. Flags plugins that were removed from the directory (with the reason), have had no release in two or more years, or are not from the directory (installed by hand or with BRAT).

Network use

This plugin sends web requests, to GitHub only. There is no analytics and no other service.

  • Once a day it reads three public files from obsidianmd/obsidian-releases (the plugin list, the removed list and the stats), the same ones Obsidian itself uses.
  • For each installed plugin from the directory, it reads that plugin's latest manifest.json from its GitHub releases, like Obsidian's own update check.
  • When you open Release notes on a row, it reads that release from the GitHub API.
  • When you choose Install an earlier version, it lists the plugin's releases from the GitHub API and downloads main.js, manifest.json and styles.css from the release you pick.

Nothing about your vault, notes or settings is sent. The requests do reveal your IP address to GitHub, as any download would. Turn off Check shortly after Obsidian starts and set Check every to Never to check only when you ask.

Commands

CommandWhat it does
Show plugin updatesOpens the list. Also on the ribbon.
Check for plugin updates nowChecks immediately and says how many updates there are.
Update all pluginsInstalls every update that is available and compatible.
Install an earlier version of a pluginChoose a plugin, then one of its previous releases, and install it.

Settings

SettingDefaultWhat it does
Check shortly after Obsidian startsonOne check about 15 seconds after startup.
Check every6 hoursWhile Obsidian stays open. 1, 3, 6, 12 or 24 hours, or never.
Show the update count in the status baronHidden at zero. Not shown on mobile.
Include pre-releases when installing an earlier versionoffAlso lists pre-releases. Drafts are never listed.

Notes

  • Updating uses Obsidian's internal plugin installer, which is not part of the public API. If a future Obsidian changes it, the plugin says so instead of failing silently; updating from Settings → Community plugins keeps working either way.
  • The plugin directory only serves the latest version of each plugin, so Install an earlier version downloads from the plugin's GitHub releases instead. Everything is downloaded and checked first (it must be the same plugin, and not need a newer Obsidian than yours). Only then are main.js, manifest.json and styles.css replaced, and if writing fails the old files are put back. The plugin's data.json is never touched. The plugin is then turned off and on again. A release without main.js and manifest.json attached cannot be installed. An older version may not understand settings a newer one saved; Update Radar cannot know.
  • Release notes are shown with code-block languages removed and [[links]] escaped, so nothing in them runs and nothing in them touches your vault.
  • Plugins with updates are installed one at a time; this plugin's own update is installed last.
  • "No release in 2+ years" uses the directory's last-release date. Plenty of finished plugins are stable rather than abandoned; the flag is a prompt to look, not a verdict.
  • Versions are compared as semantic versions, so 1.10.0 is newer than 1.9.0 and a pre-release such as 2.0.0-beta.1 is older than 2.0.0. A version that is not semver (four parts, a date) counts as an update whenever it differs, like Obsidian's own check.
  • Plugins that are not in the directory cannot be checked for updates and appear only under health.

Installation

In Obsidian, open Settings → Community plugins → Browse and search for "Update Radar".

More plugins by Siulved54

PluginWhat it doesSource
Shared BlocksWrite a block of text once and reuse it in any note. Edit the source and every reference re-renders live.shared-blocks
Text Case and CleanupChange case, make camelCase or slugs, sort lines and remove duplicates, and repair text pasted out of a PDF, without touching code or URLs.text-format
Typography as You TypeCurly quotes, dashes and ellipses as you type, kept out of code and maths, with Backspace to take one back.smart-typography-plugin
Section NumberingNumber headings as an outline (1, 1.1, 1.2) and keep every link to them working when they renumber.section-numbering
Spreadsheet to TablePaste cells from Excel or Google Sheets as a Markdown table with a real header, insert CSV files, and copy tables back out.spreadsheet-to-table
Hybrid Line NumbersRelative and hybrid line numbers for Vim-style jumps, where a folded section counts as one line.hybrid-line-numbers
List Item CalloutsColour a single list item as a callout by starting it with a character such as &, ! or ?.list-item-callouts
Folder CountsSee how many notes or files each folder holds, right in the file explorer, with a vault total and folder exclusions.folder-counts
Note Reading TimeReading time of the current note or your selection in the status bar, optionally saved to a property.note-reading-time
Task RolloverRoll unfinished tasks from your last daily note into today's when it is created, with a real undo.task-rollover
Zoom Into SectionZoom into a heading or list item to see only it and its contents, with a breadcrumb bar to climb back out.zoom-into-section
Link Title on PastePaste a web address and get a Markdown link with the page's title, fetched in the background and undone in one step.link-title-on-paste
Dataview to BasesConvert Dataview queries into Bases blocks, and see which queries in your vault can be converted.dataview-to-bases
Line Editing CommandsDuplicate, join, sort and reverse lines, insert blank lines and jump to a line number, with multi-cursor support.line-editing-commands
Note Mover RulesMove notes into folders by ordered rules on tags, properties, titles and paths, with a preview before any bulk move.note-mover-rules
Tab HistoryKeeps each tab's back and forward history across restarts, and adds commands to move, maximize and close tabs.tab-history
URL CardsShows web addresses as cards with title, description and image, and reads existing cardlink blocks.url-cards
Vim ConfigLoads a vimrc-style file from your vault so your key mappings and editor commands are ready when vim mode starts.vim-config
Task ArchiveMoves completed tasks, with their sub-items, into an archive section or note.task-archive

All of them are in the community directory: Settings -> Community plugins -> Browse, then search for the name.

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.