Plugin registry: curated index and one-action install #22

Closed
opened 2026-10-06 21:16:51 +02:00 by SBDeveloper · 1 comment
Owner

Part of #13

What to build

User browses a curated index of Plugins, installs one with the same consent flow as manual install, and sees when updates are available.

Acceptance criteria

  • Index fetched and listed via Core
  • Install from index uses the manual install flow
  • Update available indicator
  • Core integration tests against a fake index

Blocked by

Part of #13 ## What to build User browses a curated index of Plugins, installs one with the same consent flow as manual install, and sees when updates are available. ## Acceptance criteria - [ ] Index fetched and listed via Core - [ ] Install from index uses the manual install flow - [ ] Update available indicator - [ ] Core integration tests against a fake index ## Blocked by - #20
Author
Owner

Implemented in fc0d4fe: Core registry index (list, preview, install via manual URL flow, update-available flag), Plugins page registry section, integration tests against a fake index. Default registry URL in src-tauri/src/main.rs is a placeholder; override with DEEZER_CLIENT_PLUGIN_REGISTRY.

Implemented in fc0d4fe: Core registry index (list, preview, install via manual URL flow, update-available flag), Plugins page registry section, integration tests against a fake index. Default registry URL in src-tauri/src/main.rs is a placeholder; override with DEEZER_CLIENT_PLUGIN_REGISTRY.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
SBDeveloper/medley#22
No description provided.