This is your official notice that we'll be making a major security release for Sharkey on the 20th of May, 2026, between 2026-05-20T13:00:00.000Z and 2026-05-20T15:00:00.000Z. Prepare to update immediately upon release. If you are unable to update your instance at the given time, take it offline before the release.
Remote
sharkey
@sharkey@sharkey.team
sharkey 2025.4.7
0 Followers
0 Following
20 Posts
Sharkey's develop branch is now updated with all security patches. Please update if you haven't already!
#Sharkey #SharkeyDev
RE: https://sharkey.team/notes/ajm6b6j2kjf8009t
Replying to
develop has been updated! happy patching, everyone
Important Clarification: Sharkey's develop branch is affected by some of today's vulnerabilities, so instances running on development (pre-release) versions do need to update or apply mitigations!
We still haven't completed patches for the develop branch, but a candidate patch set is being tested as we speak. We'll push the changes as soon as they're done and confirmed to work!
#Sharkey #SharkeyDev
Replying to
I'm sorry, but- I'm gonna have to throw in the towel for develop for the night. For the savvy users running it, please look into forward-porting the patches for your own instance, until an official release is made.
I'm at the end of my rope for now, and need to recharge- the diff requires resolving six months of merge conflicts. You have my sincerest apologies.
Replying to
For instances of sufficiently large instance (>~50 MaU) who are unable to apply patches at that time, our maintainer (@julia@eepy.moe) would like to give a one time offer to apply patches on the behalf of instance administrators.
If you are physically unable to apply patches and meet the requirements, please direct message her for further information.
Replying to
Jumped the gun on posting this slightly, my bad!! 🙇♀️
Docker images have now been pushed. Develop is still in progress.
Replying to
@axionyx@nanotrasen.zone If its a single user instance, that would be the recommended course of action, yes.
Replying to
@frost@wolfdo.gg @markus@dresden.network gah, yeah. 2025.4.6. Got my wires crossed because of being behind on upstream and all.
Replying to
Replying to
@mjdxp@labyrinth.zone it displays using the users local time on Sharkey, which provides them with an unambiguous time for when they need to patch