Sindastra :femin:🏴‍☠️
I'm on #Misskey 2025.12.2, would a migration to #Sharkey be supported from this version and would this be a good time to use the maintenance as excuse to finally migrate? ​​

#misskeyadmin #sharkeyadmin

RE: https://sharkey.team/notes/ajka8rybkjf80061
Mar 8 at 4:49amWeb
Show threadImperatrix Siina Mar 8
@sin cc @dakkar
Show threaddakkarMar 8
@siina thank you for thinking of me 😜
@sin as the official account already said, we currently don't have a migration path from Misskey > 2025.4.1
I'm pretty sure there will be one, once we manage to catch up (it's been a long year)
Show threaddakkarMar 8
@sin oh, one detail that may not have been completely clear: there will be a Misskey release with the same fixes, at the same time as ours, so you should update to that
@julia worked her ass off to port our fixes to latest Misskey and to coordinate these releases!
@siina
Show threadSindastra :femin:🏴‍☠️Mar 8
@dakkar are the Sharkey version numbers in any way related to the Misskey version numbers (and are they any indicator of migration support?) or is this more of a coincidence? @siina
Show threaddakkarMar 8
@sin yes! Our current stable version is 2025.4.5 which is based on Misskey 2025.4.1
Next big release will probably be a bit more confusing, because it's going to be based on Misskey 2025.5.0 (not 2025.5.1) and will probably be called 2025.5.2 (we can't use the same tag name as Misskey, or all our repositories will get every confused)
@siina
Show threadSindastra :femin:🏴‍☠️Mar 8
@dakkar But at least it's safe to say that year and month are always based on Misskey versioning?

Btw. Why not do versioning like some distros where you keep the original version but add a dash and "revision"? That's how you can tell what version a distro based their package on but also if they did any changes diverging from upstream. So in this case using that logic it would be 2025.5.0-1 (if I'm not mistaken).

@siina
Show threaddakkarMar 8
@sin we will switch to something pretty similar, yes, we just hadn't thought properly about it until a few months ago (and some intrepid instances are already running 2025.5.2-dev so we can't rename it to 2025.5.0+sharkey.1…)
@siina
Show threaddakkarMar 8
@sin and yes, the idea up to now is that you can migrate from the latest Misskey release of each month to the latest Sharkey of that month
(Misskey 2025.5.1 to Sharkey 2025.5.2 may not work, though, it's a long-ish story)
@siina
Show threadSharkey - Official AccountMar 8
@sin no, that misskey version is newer than the most recent sharkey merge, so you'd be unable to migrate.
Show threadJürgen ⁂Mar 8
@sin
It would help to ask the Sharkey dev team in via Discord, they are really supportive. Caveat is, that Misskey is far behind even 2025.12.2 and there might be challenging database changes in the meanwhile.