Versioning and changelog
Versioning policy and changelog for the Safeguard AI SDKs for TypeScript, Python and Go.
Versioning and changelog
The SDKs use semantic versioning. The TypeScript, Python and Go SDKs move together. The HTTP API carries its own major version in the path (/v1) and does not break within a major version. Before 1.0, a minor SDK release may change the SDK's surface, so pin a version in production.
0.1.0 (21 November 2026)
First release of all three SDKs:
Safeguardclient withcontext(),conversations(create, list, get, messages),query()andstream().- Typed errors with
status,code, retry-after and request id; retries only where repeating a request is safe. - API key from the argument or
SAFEGUARD_API_KEY. No telemetry. - TypeScript: Node 18 or newer, ESM and CommonJS, types, no dependencies. Python: 3.9 or newer, sync and async,
httpx. Go: 1.22 or newer, standard library only.
| Language | Package | Release tag |
|---|---|---|
| TypeScript | @safeguard-sh/sdk | sdk/typescript/v0.1.0 |
| Python | safeguard-sdk | sdk/python/v0.1.0 |
| Go | safeguard.sh/sdk | sdk/go/v0.1.0 (module version v0.1.0) |
The same release is served from registry.safeguard.sh, and the npm package is also on npmjs.com with an identical checksum. See Install.
For anything the SDKs do not cover, or an API you need, write to hi@safeguard.sh.
Examples
Complete Safeguard AI SDK examples: a Node script, a Python script, a Go program and a CI job that runs one with the key from a secret.
Guard SDK
Guard agents for Node, Python, Java, .NET and Go enforce your organization's Guard policy inside your own MCP server or agent process. They are installed from registry.safeguard.sh with your organisation's pull token.