"Entry point not found" after kaju update

I maintain an xplatform desktop app that uses Kaju for updates. That usually works fine, but two customers sent tickets where after an update the app will not run anymore, with a message

The procedure entry point DatabaseColumn_ValueSetter could not be located in the dynamic link library (app.path).

Sounds to me like an incompatible binary was updated.
I am currently asking for more system information but have the inkling it could be connected to me having extended kaju with a WindowsARM branch as the app also has a native Win ARM build.
On my Win 11 ARM Parallels VM the update works flawlessly, so I wonder if there could be conditions that make it necessary to install Intel builds rather even if ARM is detected, and how to address this optimally.

Did you handle the situation where a user installs the Intel version of the app on an ARM system?

I guess this is what might be wrong in my Kaju extension. I should examine the system and not only the CPU architecture for the correct download path.
I bet there’s something in MBS (or even System?) to get this right …