2026.3.1 has been a disaster, what are the implications for rolling back to 2026.2.x?

2026.3.1 has been a disaster, what are the implications for rolling back to 2026.2.x?

avatar

Do I need to worry about database schema? Can I just install 2026.2.5 and be up and running?

All Comments (3)

avatar

I see downgrading is supported, however I don't see anywhere the schema versions are listed.

Additionally, it looks like you can't use the MSI to downgrade without first uninstalling.

Finally, the downgrading page lists the wrong command line parameters.

avatar

For anyone else considering a downgrade I was able to uninstall 2026.3.1 and install 2026.2.5 without issue.

avatar

Hello @realslacker

Thank you for coming back and sharing the outcome.

It is very helpful to know that you were able to uninstall 2026.3.1 and install 2026.2.5 successfully. This should also be useful information for others considering the same rollback path.

I also appreciate your feedback regarding the downgrade documentation, particularly the schema version information and the command parameters. We will review those points to make sure the documentation is as clear and accurate as possible.

Thanks again for contributing your findings to the community.

Best regards,
Ruben Tapia