v3.21.2

This release improves the reliability of forking nodes with multiple reference images across different providers.

Keep reference images together when forking

When forking a node that uses multiple reference images to a different model provider, all connected images now stay grouped together on the appropriate input handle. Previously, some connections could be silently dropped if the target model used different input naming conventions. This ensures your multi-image workflows maintain consistency when switching between compatible models.