Operate and upgrade TypeBridge¶
Operational choices depend on the execution boundary and TypeDB version, not on a separate semantic implementation.
Run¶
- Server container covers immutable images, non-root execution, TLS, V2 authority configuration, health checks, and supply-chain verification.
- Logging covers the Python logger hierarchy, query visibility, sensitive data, and debugging.
- TypeDB compatibility records supported servers, driver bands, interpreters, native targets, and feature gates.
Upgrade¶
Read Upgrading to 2.3 before moving a 2.2 application to 2.3. Read Upgrading to 2.1 before changing an existing 2.0.x application. It separates the source-compatible package upgrade from later, explicit adoption of V2 schema and query surfaces.
The V2 deprecation inventory is the exact removal contract. A surface absent from its scheduled-removal list is not implicitly scheduled for removal.
Security boundaries¶
Use immutable release identities, provision credentials outside committed configuration, authenticate remote capability advertisements, and bind V2 execution to the intended canonical schema. Detailed limits and trust inputs remain in the server, typed-query, migration, and upgrade guides rather than being duplicated here.
Python provider failures expose an immutable error.failure dataclass with
phase, reason, lock_kind, annotation, op_index, retry_safe and
code. Ordinary commit errors remain catchable as RuntimeError and use
CommitRejected, its CommitConflict subclass, or CommitOutcomeUnknown,
exported by type_bridge. Existing structured-query exception ancestry stays
unchanged. A rejection permits rerunning the entire transaction on a fresh
snapshot; an indeterminate commit must be reconciled before retrying.