Re: Database Migrations—Are Minor Upgrades Okay? (e.g. 6.1.0 -> 6.2.0)

Feedback
1

Reading this, I see database migrations need to be done between versions, so they can’t be skipped: https://docs.rocket.chat/setup-and-configure/advanced-workspace-management/database-migration

I’m deploying through Docker. My understanding of Rocket.Chat versioning is:

Major.Minor.Patch

My understanding is that Minor upgrades should not be skipped, but skipping Patch versions is okay. So these would be supported:

6.1.0 -> 6.2.0

6.2.1 -> 6.2.10

But this would not be supported:

6.0.0 -> 6.2.0

Is my understanding correct? Or do I really need to go through every Patch release?

I see there is a list of migrations here, but they don’t have versions on them as far as I can tell: https://github.com/RocketChat/Rocket.Chat/tree/develop/apps/meteor/server/startup/migrations

2

Got a response from Matheus Barbosa Silva:

You can jump through minors (first and second options are ok) and you’ll get every missing migration in the process