Em 
Mastodon EngineeringWe just released Mastodon 4.5.9, 4.4.16, and 4.3.22.
These versions contain various bug fixes, including important security fixes.
Full release notes and update instructions are available on the GitHub releases page.
4censord 
@MastodonEngineering the linked security advisory 404s, is that intended?
@4censord Fixed, thanks for noticing!
Lizzie@MastodonEngineering of I'm a senior citizen here for gardening and hating the orange pustule, should I be doing something to upgrade?
Fargate 
@Lizette603_23 @MastodonEngineering Normal users don't need to do anything, the update will be performed by the ones operating the service. I see you are on the flagship instance mastodon.social, so that'll be one of the first to upgrade and seems to already have done so.
@fargate @MastodonEngineering so kind to respond. Thanks a bunch
Luca Sironi@Lizette603_23 @MastodonEngineering
No, you are fine.
this is for server administrators to do.
NicholasR😊@Lizette603_23 @MastodonEngineering these are Mostodon software releases for the server software. If the server instance you are connected to upgrades to the latest release, the only thing you need to do is F5 refresh your web browser tab and you will have any new features available to you.
connie!!? 
🌈 Andrew ☄️@MastodonEngineering I’ve noticed you supporting older versions like this before. OOI do you know why people don’t want to upgrade? Or is there some other reason you’re supporting old versions?
Fox Ritch 
🇩🇪@bnut @MastodonEngineering I can understand not updating cause mastodon is a pain to update but like keeping older branches alive is wackass. I wanted to see if I could sort by version on fedilist.com, which I couldnt, but I found something very shocking:
Out of the top 10 biggest mastodon instances(by user), 4 use a version of 4.1.x💀💀💀
@MastodonEngineering and my ass over here still on v4.5.0 cause mastodon is a bitch to update
Jef Poskanzer@MastodonEngineering I'm still getting "Uncaught TypeError: Object.hasOwn is not a function". You have fixed this exact bug at least twice before, how about fixing it again?
@jef @MastodonEngineering how about throwing everything in the trash and starting again. I probably did that once or twice to fix the jank that mastodon is
@MastodonEngineering Also, how about adding a "console.log(version)" call very early? So that when it crashes while loading, we can still find the version in the web console and put it in the bug report.
defnull@jef @MastodonEngineering But ... Object.hasOwn *is* a function? At least in all browsers released in the last 5 years? I seriously do not understand how this error can happen in a modern browser. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/hasOwn
Renato, aka Krull@MastodonEngineering @meatlotion Guess what? :