Publish labels and roll back
Move stable application selectors between saved versions.
A label is a named pointer to a saved version. Applications can follow production while your team tests a different version through staging. Saved version numbers are immutable; labels move as your release decisions change.
Assign a label
Open a saved version's label controls, inspect the currently assigned version, and select the version you want. The initial baseline assigns both built-in labels to version 1. Later saves leave those assignments unchanged.
Assign staging for an integration check, then production when you decide to release. Production publication can warn that the version is unevaluated, that the dataset changed since evaluation, or that only Quick coverage is available. Review the warning and acknowledge it if you choose to proceed. Publication does not impose a universal passing-score threshold for your team.
Screenshot placeholder — Publish with coverage context Show the target saved version, current production assignment, coverage information, and the publication confirmation.
With the API, an acknowledgment is bound to the publication context returned by the server. Read the response and resubmit only after reviewing that exact warning; do not reuse an acknowledgment for an unrelated version or later dataset state.
Roll back
Select an earlier saved version and assign production to it. The next server retrieval sees the completed label move. Applications that cache responses must revalidate to observe the change.
Rollback preserves all versions and evaluation results. It does not reset your draft or delete the candidate that caused the regression.
Custom labels and conflicts
Create a custom label for a stable environment name such as qa. Names use lowercase letters, digits, and hyphens, start and end with a letter or digit, and contain at most 64 characters. An unassigned label returns an error on retrieval; it does not fall back to production.
The built-in staging and production labels cannot be renamed or deleted, and production cannot be unassigned. Label mutations check a revision. If someone moves a label while you are reviewing it, reload and confirm the current target before trying again.