#
How Minor Model Updates Are Introduced
Minor updates follow a structured preview, validation, and promotion process to keep model identifiers stable while improving the underlying model.
#
The update process
Preview: We make a candidate minor update, such as
GLM 5.4-preview, available for at least one month.Validation: During that month, we check compatibility, model behavior, and operational readiness. We encourage customers to test the preview with their own prompts, integrations, and workflows.
Pricing: Before adopting the update, we confirm that its price is no higher than the current major-version offering.
Promotion: If validation is successful, we update the model behind the existing major-version API identifier. Applications can continue to use the same model name.
Because model responses can vary, a successful validation does not guarantee identical outputs. If your application depends on specific behavior, we recommend testing it against the preview before the update is promoted.