@sin cc @dakkar

@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)

@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

@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

@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