If you are upgrading any version of SNAPSHOT to new version you should always run @upgrade-schema@. This is a good practice and this way you can be sure that you are using the correct version of the database schema.

And answering your question: Yes, upgrade of the database schema is required for this new version (with authentication changes) to work properly.

%andrzej.wojcik , do we still have and use DB schema versioning? Shouldn't the DB schema checking code discover that the schema needs upgrade?

From what I know %wojtek is still working on the version checking, but schema versioning and checking will work fine in release version but not between snapshots from what I know. But let’s wait for Wojtek to confirm that.

Andrzej Wójcik wrote:

From what I know wojtek is still working on the version checking, but schema versioning and checking will work fine in release version but not between snapshots from what I know. But let’s wait for Wojtek to confirm that.

%kobit

As described in https://tigase.tech/projects/private/wiki/Schema_files_maintenance we agreed with Andrzej that:

SNAPSHOT versions will print a log entry indicating that there may have been a changes in schema and it's recommended to run the upgrade (we are aiming at frequent releases thus mandatory schema version check will be done only with final version)

For a long time we were recommending upgrading to the testing (SNAPSHOT, nightly) which is rather wrong practice. We should prepare a solid and stable product that would be released frequently (1-2 times a year) and support smooth upgrade to the subsequent version. In case of someone going with testing route there would be an inconvenience of notification that they are using snapshot and should run @upgrade-schema@. While we could handle this case as well this would only unnecessarily complicate the whole mechanism.