Keysat
14 lines
1.5 KiB
TypeScript
14 lines
1.5 KiB
TypeScript
import { VersionInfo } from '@start9labs/start-sdk'
|
|
|
|
export const v_0_2_85 = VersionInfo.of({
|
|
version: '0.2.85:0',
|
|
releaseNotes: {
|
|
en_US:
|
|
"Route everything through Spark Control as the single host for operator-hardware calls. Before: transcribe went to the Parakeet wrapper at 192.168.1.87, analyze went to vLLM at 192.168.1.103, diarize went to Spark Control at 192.168.1.72 — three hosts for one logical pipeline, with the transcribe + analyze hosts unable to serve diarize. After: all three calls (POST /v1/audio/transcriptions, POST /api/audio/diarize-chunk, POST /v1/chat/completions) go to Spark Control's own base URL. The relay still reads /api/endpoints discovery, but ONLY to learn (a) which services are ready and (b) what model name is loaded on each — the per-service base_urls discovery reports are informational, used in the dashboard's Service Discovery health line so you can see what Spark Control's delegating to internally. Switched all hardware-backend fetches (transcribe POST + retry, diarize POST, analyze POST, /v1/models autodiscovery) to lanFetch so Spark Control's StartOS Local CA cert over HTTPS passes TLS validation. Net effect: one operator-facing config (Service Discovery URL) drives everything; no per-endpoint URLs anywhere in code or config; the diarize path that was 404'ing because it hit the parakeet wrapper now resolves correctly because it's pointing at the host that actually serves it.",
|
|
},
|
|
migrations: {
|
|
up: async ({ effects }) => {},
|
|
down: async ({ effects }) => {},
|
|
},
|
|
})
|