Migrating to InvokeAI v5.12.0rc2
Version v5.12.0rc2 introduces 2 breaking changes. This guide details how to update your code.
Released: 5/21/2025
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
ImageFieldBaseInvocationInputFieldGGMLTensorBaseModel.model_fieldsBreaking Changes
●Issue #1
Default values for node fields are now strictly validated upon application startup. If a node defines a field with a default value that does not match the field's type annotation (e.g., providing `None` for a non-optional `ImageField`), the application will error on startup. To fix, either update the type annotation to include `| None` (e.g., `ImageField | None`) if the field is optional, or remove the invalid default value or provide a valid one.
●Issue #2
The previous IP Adapter style method has been renamed to `Style (Simple)`. Code relying on the old name for the simple style method must be updated to use `Style (Simple)`.
Migration Steps
- 1If you are a node developer, review all custom nodes to ensure default values strictly adhere to their type annotations. Update optional fields to use `| None` or remove invalid defaults.
- 2If you use the IP Adapter style method in scripts or configurations, rename references from the old style method name to `Style (Simple)`.
Release Summary
This release introduces support for Nvidia 50xx GPUs and a new model relationship feature for linking LoRAs. It also enforces stricter validation on node default values, which may require updates for custom node developers.
Need More Details?
View the full release notes and all changes for InvokeAI v5.12.0rc2.
View Full Changelog