Energy-Alpha patches a profile-update mismatch before it breaks the frontend
A small compatibility fix lets two ways of saving a user profile work reliably with the same backend.
Energy-Alpha has added support for a second, widely used method of submitting profile changes. The underlying profile checks, update process and account-key status all remain the same; this is about accepting the request shape an existing frontend was already sending.
It looks like a focused production hotfix rather than a broader product change, including a follow-up redeploy. That makes it useful if your own Mike interface is failing when users try to save profile changes, but not a must-have feature for every fork.
The implementation currently repeats the same update logic in two places, so anyone adopting it may want to consolidate that later.
Who should care: teams maintaining a customised Mike frontend, where a minor integration mismatch can otherwise block a basic account-setting workflow.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?