Repository navigation
Replies: 1 comment 2 replies
|
The important distinction is between built-in plugins and registry-backed external plugins. Built-in plugins ship inside the app bundle, so they update with app releases, not through the plugin registry UI. The registry is for external distributable plugins: it provides metadata plus one or more release entries with version, compatibility requirements, size, and a ZIP download URL. On the next version, TypeWhisper fetches the registry in the background, resolves the newest release compatible with the current app version, macOS version, and architecture, and compares that against the installed external plugin bundle. If the installed plugin is not built-in and the registry has a newer compatible version, the Integrations screen shows Update. Manual plugins that are not in the registry can still be installed from .bundle or .zip, but they will not participate in automatic update discovery unless they have a registry entry. |
|
So how would I currently update the ParakeetPlugin to v1.2.5 for example? The last typewhisper version was 1.2.2 but the ParakeetPlugin was updated afterwards |
|
One important nuance here: this changes in the 1.3 RC line. Older builds use the legacy marketplace feed, but 1.3+ switches to the new v1 registry flow with compatibility-aware plugin resolution and multi-release metadata. So if you are looking at the next version, it is not just “plugins update the same way” the registry / JSON side is materially different there. |
One important nuance here: this changes in the 1.3 RC line. Older builds use the legacy marketplace feed, but 1.3+ switches to the new v1 registry flow with compatibility-aware plugin resolution and multi-release metadata. So if you are looking at the next version, it is not just “plugins update the same way” the registry / JSON side is materially different there.