Skip to content

fix(driver-turso)!: refuse timeout beside an UPPERCASE WSS:// url in forced remote mode #22732

fix(driver-turso)!: refuse timeout beside an UPPERCASE WSS:// url in forced remote mode

fix(driver-turso)!: refuse timeout beside an UPPERCASE WSS:// url in forced remote mode #22732

Triggered via pull request September 8, 2026 10:29
Status Success
Total duration 59s
Artifacts

pr-automation.yml

on: pull_request
Check PR Size
16s
Check PR Size
Check Changeset
55s
Check Changeset
Auto Label
16s
Auto Label
Fit to window
Zoom out
Zoom in

Annotations

1 notice
Check Changeset: .changeset/driver-turso-uppercase-ws-scheme-timeout-refusal.md#L0
ADR-0087 exemption (no-migration-prescription): An accept-set narrowing performed at the driver constructor: no key, spec symbol, Zod schema, object definition or stored representation is added, removed or renamed — `TursoDriverConfig.timeout`, `url` and `mode` keep their names and types, and `TursoConfigSchema` is untouched. What moves is which CONFIGURATIONS `new TursoDriver()` accepts — one predicate now compares the url's scheme case-insensitively, exactly as `@libsql/client` itself does before routing — so `objectstack migrate meta` has nothing to visit and there is no tombstone to mint. The refusal is the one the lowercase spelling already produces, naming the key, the scheme it met and both ways out; which of the two an author wants is authoring intent no ledger line can decide.