This is your official notice that we'll be making a major security release for Sharkey tomorrow (between 2026-03-08T22:00:00.000Z and 2026-03-09T00:00:00.000Z) in coordination with Misskey. Please be ready to patch your instances soon as humanly possible, as the vulnerabilities at play are extremely severe. Note that IceShrimp and Firefish derivatives are not affected, only direct forks of Misskey.
Timeline
Post
Remote status
Context
8@sharkey@sharkey.team thats awesome but i will simply not
@wiki@please-dominate.me @sharkey@sharkey.team please do it genuinely is like unsafe to your users to not apply this
@julia@eepy.moe @sharkey@sharkey.team julia i am 3 years out of date
the database cant migrate properly so im stuck like this
@wiki@please-dominate.me @sharkey@sharkey.team what the fuck did you do
@julia@eepy.moe @sharkey@sharkey.team well i didnt update for long enough to the point its just so different that the automatic migration wont work
thats probably the reason according to lea atleast
@wiki@please-dominate.me @sharkey@sharkey.team you should be able to update version by version, applying specific migration nodes as needed
@julia@eepy.moe @sharkey@sharkey.team any way to see which versions i should be going to
Replies
1@wiki@please-dominate.me @sharkey@sharkey.team the sharkey changelog should include a comprehensive list of updates that require SQL intervention