kaitranntt 2a0efbd954 fix(cliproxy): propagate backend parameter to version check functions ...

Root cause: fetchLatestCliproxyVersion() and checkCliproxyUpdate()
ignored the caller's backend selection, always re-computing from config.
This caused --update to report wrong version when config wasn't synced.

Changes:
- Add optional backend param to fetchLatestCliproxyVersion()
- Add optional backend param to checkCliproxyUpdate()
- Pass effectiveBackend in binary-service.ts calls
- Pass backend in cliproxy-stats-routes.ts web endpoints

Fixes inconsistent version reporting when switching between
CLIProxyAPI (original) and CLIProxyAPIPlus backends.

2026-01-23 22:56:27 -05:00

..

binary-service.ts

fix(cliproxy): propagate backend parameter to version check functions

2026-01-23 22:56:27 -05:00

index.ts

refactor(cliproxy): extract service layer from cliproxy-command

2025-12-19 11:48:45 -05:00

proxy-lifecycle-service.ts

refactor(cliproxy): extract service layer from cliproxy-command

2025-12-19 11:48:45 -05:00

variant-config-adapter.ts

fix(dashboard): support unified config.yaml in web server routes

2025-12-26 13:37:54 -05:00

variant-service.ts

feat(cliproxy): add backend selection for CLIProxyAPI vs CLIProxyAPIPlus

2026-01-18 10:10:01 -05:00

variant-settings.ts

Merge pull request #184 from kaitranntt/kai/feat/variant-port-isolation

2025-12-25 05:19:06 -05:00