Migrating to InvokeAI v5.12.0
Version v5.12.0 introduces 1 breaking change. This guide details how to update your code.
Released: 5/22/2025
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
ImageFieldBaseInvocationInputFieldGGMLTensorSAMBreaking Changes
●Issue #1
Node default values are now strictly validated at application startup. If a node defines a field (e.g., ImageField) with a default value that does not match the field type (e.g., default=None), the application will error on startup. Fix by either updating the type annotation to include None (e.g., ImageField | None) if the field is optional, or by removing the invalid default or providing a valid default value that satisfies the field constraints (e.g., for an integer field with gt=10, the default must be > 10).
Migration Steps
- 1Node authors must review their custom nodes to ensure all InputField default values are valid according to their type annotations, or update type annotations to allow None if the field is optional. Nodes failing validation will cause application startup failure.
- 2Users are recommended to use the new Invoke Launcher for installation and updates, following the Quick Start guide.
Release Summary
This release introduces support for Nvidia 50xx GPUs via a PyTorch bump, adds model relationship management, and implements stricter validation for node default values, which may require updates for custom node authors.
Need More Details?
View the full release notes and all changes for InvokeAI v5.12.0.
View Full Changelog