Transformers releases v5.10.2: fixes CLIP model conversion defects and consolidates the v5.10 series
Transformers v5.10.2 patch version fixes CLIP model conversion defects; v5.10.1 introduces new models such as Gemma4, Sapiens2, DeepSeek-OCR-2 and Mellum, and v5.10.0 has been withdrawn.
Transformers v5.10.2 is launched: a patch for CLIP stabilizes the v5.10 series
Transformers Release v5.10.2 patch version. In one sentence: This is a finishing patch - it fixes the CLIP model conversion defect and brings the v5.10 series, which was slightly turbulent due to the withdrawal of v5.10.0, back to a state where dependencies can be pinned with confidence.
Understand at a glance
| Project | Content |
|---|---|
| Version number | v5.10.2 (patch) |
| Nature | Bug fixes, no breaking changes |
| Core Fixes | CLIP model conversion bug (#46406) |
| Supporting features | New model support following v5.10.1 |
| Notes | v5.10.0 has been withdrawn (yanked) |
v5.10 What happened to this series of versions?
Putting the three small versions together, the logic becomes clear:
| Version | Status | Key Points |
|---|---|---|
| v5.10.0 | Withdrawn | Installation not recommended, please avoid being locked into this version |
| v5.10.1 | Feature version | Added Gemma4, Sapiens2, DeepSeek-OCR-2, Mellum and other models |
| v5.10.2 | Current recommendation | Fix CLIP conversion defects and inherit all new models of v5.10.1 |
In other words, the new model capabilities come from v5.10.1, and v5.10.2 is responsible for filling in the known defects on this line - the two together are the stable combination that should be used currently.
Who needs to move now?
- Projects relying on CLIP load/transform links: upgrade directly, circumventing #46406.
- Projects that previously had their dependencies locked at v5.10.0: change the pin to v5.10.2 as soon as possible.
- Teams who want to use new models such as Gemma4 / DeepSeek-OCR-2: v5.10.2 already comes with these supports, and there is no need to fall back to the feature version.
Tips before and after the upgrade
- Pin the dependency to v5.10.2 instead of the withdrawn v5.10.0.
- After the upgrade, perform a round of regression on CLIP and multi-modal reasoning to confirm that the outputs are consistent.
- The detailed behavior of individual models may still be affected across small versions. It is recommended to verify it in the test environment first; the individual changes and the list of affected models shall be subject to the official release notes.
Reviews