You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/docs/plugins/plugin-store.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ After installation, the plugin appears in the Installed tab. Toggle it on to ena
24
24
25
25
You can also install plugins from a local folder. In the Installed tab, click "Add Plugin" and select a folder containing a plugin (a directory with a `package.json` and an entry file).
26
26
27
-
Manually installed plugins have one extra feature: a reload button. Click it to re-read the plugin source from the original folder, recompile, and reload. This is useful during development. Store-installed plugins don't support reload; remove and reinstall to get a new version. Auto-update is planned for the future.
27
+
Manually installed plugins have one extra feature: a reload button. Click it to re-read the plugin source from the original folder, recompile, and reload. This is useful during development. Store-installed plugins don't support reload; remove and reinstall to get a new version. Store plugins are updated automatically on startup (see Plugin updates below).
28
28
29
29
## Managing plugins
30
30
@@ -44,7 +44,11 @@ Dev plugins show a reload button that re-reads the source from the original fold
44
44
45
45
## Plugin updates
46
46
47
-
There's no automatic update mechanism yet, but it's planned for the future. To update a store-installed plugin, remove it and reinstall from the store. Nuclear always fetches the latest GitHub release, so reinstalling picks up any new version the developer has published.
47
+
Nuclear checks for updates when it starts. If a newer version is available in the registry and auto-update is enabled (the default), the update is downloaded and installed automatically. The old version's files remain on disk but the new version takes over.
48
+
49
+
To disable auto-update, go to Settings and turn off "Auto-update plugins" under the Plugins section.
50
+
51
+
Dev plugins are never auto-updated. To update a dev plugin, edit the source and click reload.
@@ -130,7 +133,10 @@ Set up CI to build and create the release automatically. Manual zip creation is
130
133
|`author`| yes | 1-64 chars. |
131
134
|`repo`| yes |`owner/repo-name` format. |
132
135
|`category`| yes | Must match your `package.json``nuclear.category`. |
136
+
|`categories`| yes | Array of categories matching your plugin's provider types. Same valid values as `nuclear.categories` in package.json. |
133
137
|`tags`| no | Up to 10 tags, lowercase with hyphens, unique. |
138
+
|`version`| no | Latest released semver version. Populated automatically by CI. |
139
+
|`downloadUrl`| no | Direct URL to the latest `plugin.zip`. Populated automatically by CI. |
134
140
|`addedAt`| yes | ISO 8601 datetime (e.g., `2026-01-25T00:00:00Z`). |
135
141
136
142
---
@@ -142,7 +148,7 @@ You don't need to update the registry to release new versions. Create a new GitH
142
148
Only submit a registry PR if you need to change the plugin's metadata (description, category, tags, etc.).
143
149
144
150
{% hint style="info" %}
145
-
There is no automatic update push to users who already have your plugin installed. They need to remove and reinstall to get the latest version.
151
+
Nuclear checks for plugin updates on startup. If auto-update is enabled (it is by default), installed store plugins are automatically updated to the latest version. Users can disable this in Settings under Plugins.
0 commit comments