@stolyarovmn/dsh-ui-registry-aggregator 0.4.16 → 0.4.17

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +10 -12
  2. package/lib/client.js +688 -237
  3. package/package.json +6 -6
package/README.md CHANGED
@@ -29,19 +29,17 @@ Search across connected sources, filter results, inspect evidence, and install a
29
29
  - **Fallback command** — installable results also expose their `dsh plugin add …` command.
30
30
  - **Responsive popularity metadata** — missing GitHub star counts are hydrated after Browse renders, so GitHub metadata cannot block the initial search result.
31
31
 
32
- ## What's new in 0.4.16
32
+ ## What's new in 0.4.17
33
33
 
34
- 0.4.16 brings Registry Aggregator directly into the native DSH Plugins page and hardens Installed/Browse metadata behavior.
34
+ 0.4.17 promotes the tested `0.4.17-rc.3` build and adds native plugin update workflows while preserving the Plugins-page integration introduced in 0.4.16.
35
35
 
36
- - Registry UI self-embeds below native **Installed** on stock DSH; no manual DSH UI patch is required.
37
- - Native Installed cards gain expandable registry metadata and advisory update badges without replacing DSH controls.
38
- - Installed metadata uses exact npm package lookup with 30-day downloads, GitHub stars/freshness, bundle verification, and DSH compatibility.
39
- - Expanded Installed cards reuse the same visual card primitives as Browse while suppressing information already shown by the native card.
40
- - Missing GitHub stars are resolved before **Stars** sorting, so displayed values and server-side order stay consistent.
41
- - GitHub stars use the same warning/yellow treatment in Browse and Installed.
42
- - Browse preferences persist across openings, including query, filters, ordered sorts, and page size.
43
- - DSH compatibility is resolved from the active runtime and declared DSH peer ranges.
44
- - Source metadata/evidence caches are bounded and identical in-flight requests are coalesced.
36
+ - Installed bundles and Registry **Updates** cards can start updates through the native DSH Plugin Manager.
37
+ - **Update all** runs available updates sequentially and can cancel the active/remaining queue.
38
+ - Individual update operations expose native progress/cancellation through Plugin Manager request ids.
39
+ - Installed Browse results with a newer discovered version expose **Update** instead of a disabled install action.
40
+ - **Add a new source** is substantially more compact, with icon-only Cancel/Add actions inline with the fields on desktop.
41
+ - Registry controls, borders, radii, links, and state colors are aligned with the DSH `0.1.7-rc.2` visual language used by this release.
42
+ - DSH runtime dependencies, declared compatibility, and the install smoke test target `0.1.7-rc.2`.
45
43
 
46
44
  Tested with DSH `0.1.7-rc.2`.
47
45
 
@@ -173,7 +171,7 @@ The order in which criteria are enabled defines priority.
173
171
 
174
172
  ## Compatibility
175
173
 
176
- - DSH: `>=0.1.7-rc.1 <0.2.0`
174
+ - DSH: `>=0.1.7-rc.2 <0.2.0`
177
175
  - Tested with DSH `0.1.7-rc.2`
178
176
 
179
177
  Exact package compatibility is read from package metadata when a publisher declares it. Installation is validated again by the native DSH Plugin Manager.