Repository navigation
v0.0.28
Highlights
Broader PII filter coverage. With the PII filter enabled, every request field except model is now scanned, not only the standard chat, completion and embedding fields. Provider-specific fields such as chat_template_kwargs or metadata, and the inputs of rerank and score requests, are pseudonymized before they reach an external provider and restored in the response as before. (#240)
Security
- Security hardening of the PII filter. (#240)
- Dependency update addressing an upstream security advisory in gRPC. (#235)
We recommend all users upgrade.
Upgrade notes
- With the PII filter enabled, more request fields are pseudonymized.
- Function and tool names must be identifiers (
A-Z a-z 0-9 _ . + -, up to 128 characters) and must not look like personal data. A name that looks like an email address or contains a phone, tax or card number is rejected with 422. logit_biasmust map token IDs (up to seven digits) to numbers; other shapes are rejected with 422 when the PII filter is enabled.
Full changelog: v0.0.27...v0.0.28