v1.60

Release notes

1.60.0

✨ New features

• Vendors
  Create and manage vendor profiles, attach supporting documentation, and see how many Use Cases are linked to each vendor. Link vendors to a use case on the use case details page.

• Reference JSON schema v2.0.0
  Model, explainer, and transformer references now support schemaVersion: "2.0.0". The new schema introduces a more explicit structure where each Deployment backend has its own dedicated shape, replacing the flat field layout of v1. References without a schemaVersion field continue to be treated as v1. The default version will change to "2.0.0" in a future release, so migrate your existing references.

• Retirement stage for Use Cases
  Use Cases can now be transitioned to a Retirement stage from any existing stage in the Use Case lifecycle. You can also configure controls specific to the Retirement stage.

• Alerts for feature drift distribution
  You can now configure alerts on feature drift distribution.

🛠️ Improvements

• Spans per service on the tracing page are now more clearly separated visually.
• Applied input and output guardrails are now visible on the request log page instead of the prediction log page. Prediction logs show the masked input and output where applicable.
• Use Cases can now only be reviewed by one of their owners.
• Filters for risk classification, stage, and role are now available on the control list.
• Improved the update flow for Deployments without a Repository.
• Updated Swagger documentation descriptions for numerical enums.
• Added a tracing code snippet.

🐛 Bug fixes

• Fixed an issue where creating external Deployments resulted in a stuck deploying state.
• Fixed an issue where the guardrail monitoring graph showed incorrect alert rule thresholds.