This week we moved Yeethook onto the newest version of the framework it is built on. Most of that work is invisible by design: your webhooks kept flowing the whole time, and there is nothing you need to change.
A few things you will notice, and a few you will not but should know about.
Pages show up faster
The dashboard now draws its frame immediately and fills in each section as its data arrives, instead of waiting for everything before showing anything. Switching between Events, Apps, and Channels feels closer to instant, because the page you just left stays ready in the background.
The public side of the site, including the docs, the event reference, and the glossary, is now prebuilt ahead of time, so those pages load straight from the edge.
Your Key ID fills itself in
When you create an App Store Connect API key, Apple names the download after the key: AuthKey_ABC123DEFG.p8. Yeethook now reads that file name when you upload the key and fills in the Key ID for you, whether you click to choose the file or drag and drop it. It also handles the AuthKey_ABC123DEFG (1).p8 name you get after downloading the same file twice. One less value to copy out of App Store Connect, and one less place for a typo.
This one came from Emin. Thank you for a great idea, Emin.
Team data is more tightly isolated
Every team's data was already kept separate at the database level. We tightened those rules further and added a large set of automated tests that try to reach another team's data.
Safer Slack messages
Some text in a notification comes from people outside your team, like a TestFlight tester's feedback or a tester's name. Slack treats a few characters as commands, so a comment containing <!channel> could have pinged everyone in the channel.
Yeethook now escapes that text before it reaches Slack. Tester feedback shows up exactly as written, and it can no longer mention the whole channel or dress up a link. Discord messages already worked this way.
The chart now includes today
The "Events over time" chart on the dashboard covered the last 30 days, but it stopped at yesterday. On a new account, that meant an empty chart next to counters that clearly showed events. It now runs through today, so the event you just received shows up right away.
Nothing to do on your side
There was no downtime, no change to your webhook URLs, and no need to reconnect Slack, Discord, or your API key. If anything looks off, the chat button in the corner reaches us directly.