GitHub Repo
Transformers 5.23.0 Unifies Model Export Objects, Requiring Deployment Workflow Updates
Hugging Face released Transformers 5.23.0 on November 13, introducing ExportedModel to unify export, storage, and loading across multiple backends. The change improves traceability of deployment artifacts and requires compatibility updates to existing export code.

Hugging Face released Transformers 5.23.0 on November 13. One update with a direct impact on deployment toolchains is that model exports now consistently return ExportedModel. The new object connects exported artifacts from Dynamo, ONNX Runtime, OpenVINO, and ExecuTorch, and provides interfaces for saving, uploading to the Hub, reloading, and calling the model. Release notes
Previously, the object returned by export() depended on the backend, and storage methods were spread across different configuration fields. The new version adds export.json, which records each component’s files, export configuration, input shapes and data types used during tracing, package versions, and input and output names. For teams maintaining multiple deployment formats, this provides a shared way to describe artifacts and helps clarify how a model was converted and what inputs it requires. This engineering benefit comes from consistent interfaces and metadata. Pull request
When upgrading, check code that directly uses the return value of an export. To access the underlying graph, use .program; for multi-component models, use .components[name].program. The output_path fields previously found in OnnxConfig and OpenVINOConfig have been removed; use save_pretrained() to save instead. Custom exporters must also implement the new export, save, and load methods, and update how they register backends. Interface changes
Generative models still require additional integration work. The official documentation explains that export_for_generation() separates prompt prefill from token-by-token decoding, and multimodal models may also split out an encoder. These are independent computation graphs, so callers still need to manage data flow and the generation loop. A unified export object therefore does not, by itself, provide a complete text-generation service. Export documentation
Exporters are still experimental, and some patches depend on specific upstream versions. Engineering teams should pin dependencies, validate save-and-reload results with representative inputs, and check caching and dynamic shapes. API stability and backend compatibility remain areas to monitor. The official release provides no unified benchmark that would support conclusions about performance gains across all models. Limitations and version guidance