easterbrooka renames Mike to Michelle and lets one backend serve many front ends
A cosmetic rebrand rides along with a quietly useful change to how the backend decides which sites it will talk to.
The visible move is a name change: across the sidebar, the browser tab, the column prompts, and the API-keys screen, "Mike" becomes "Michelle." The icon stays put; only the words change. Mechanical, reversible, and entirely cosmetic.
The more interesting change sits in the plumbing. Previously the backend would only trust requests coming from a single approved web address. easterbrooka reworked it to accept a list - so a production site and a staging site can both talk to the same backend without anyone touching the code. Requests from any address not on the list are turned away, which is the safe default. The one wrinkle: the approved addresses are now packed into a single comma-separated setting, so whoever configures the deployment needs to know that format.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?