Versioning: answer first
Mistral positions Studio as a system of record for prompts and skills with immutable versions, owners, history, lineage, classification labels, and audit logs. Use those records to answer “what ran?”—then keep separate evidence for tests, approval, deployment, and downstream effects.
Minimum version record
Record the asset ID, owner, immutable version, change reason, model and tool dependencies, dataset and evaluator versions, test result, risk review, label, promoter, deployment target, activation time, and rollback candidate.
Safe rollback procedure
- Stop or contain the harmful path when needed.
- Identify the exact version and executions affected.
- Compare the current and known-good versions plus dependencies.
- Run the critical regression set against the rollback candidate.
- Promote through the normal approval path.
- Verify production telemetry and downstream systems.
- Repair or communicate external effects separately.
“Known good” is scoped evidence, not an eternal quality label. A version can be safe for one model, tool set, language, dataset, or policy and unsafe for another.
Frequently asked questions
Can an immutable version be edited?
Mistral says recorded versions are fixed. Create a new version for a change.
Are labels the same as environments?
No. A Production or Staging label is a classification and lookup mechanism; verify actual deployment and runtime evidence.
Where should production promotion be controlled?
Use the CI/CD promotion guide and preserve required tests and approvals.
Official sources
Source check: August 5, 2026.