How Versioning Works
Each model version progresses through four stages:- Alpha: New version available for opt-in testing via the
alphaconfig - Default: Automatically used for all requests
- Deprecated: Old default, still accessible via
alphaconfig - Removed: No longer available
Rollout Process
New model versions follow a 4-week rollout window:- Weeks 1-2 (Alpha): The new version is available for opt-in testing. You can pin to the new version via the
alphaconfig to evaluate it against your workloads before it becomes the default. - Week 3 (Default): The new version becomes the default for all requests. The previous default is demoted to deprecated status.
- Weeks 3-4 (Deprecated): The previous default remains accessible via version pinning for 2 weeks after being replaced. Use this window to migrate any workflows that depend on the old version’s behavior.
Reducto is deployed as a monolith, so fully frozen snapshots of previous versions are not available outside of on-prem/VPC deployments. Version pinning during the rollout window is the supported mechanism for managing behavioral changes.
Pinning a Version
To pin a specific version, pass it in your request’ssettings.alpha config:
Model versioning only changes processing behavior. It does not break the API contract. If a pinned version is unknown or has been removed, the request returns an error listing the available versions.