3e89b30b3c
* fix: use full update path when --custom-source is passed with --yes When --yes is used on an existing install, the installer auto-selects quick-update. However, quick-update never re-clones custom module repos — it only reads whatever is already in the cache. This means --custom-source with a new version tag (e.g. @1.1.0) is silently ignored and the previously cached version (e.g. 1.0.1) is reported as "already up to date". Default to the full update path when --custom-source is present, so the custom repo gets re-cloned at the requested version. Also ensure all installed modules are included in the selection when --yes is combined with --custom-source, preventing previously installed modules from being removed. * fix: address review feedback on choices.find() and comment clarity * style: prettier fix for empty-body methods in custom-module-manager --------- Co-authored-by: Brian <bmadcode@gmail.com> |
||
|---|---|---|
| .. | ||
| channel-plan.js | ||
| channel-resolver.js | ||
| community-manager.js | ||
| custom-module-manager.js | ||
| external-manager.js | ||
| official-modules.js | ||
| plugin-resolver.js | ||
| registry-client.js | ||
| registry-fallback.yaml | ||
| version-resolver.js | ||