I’ve checked on my side, I don’t see any update attempt on the agent version of your production and staging environments.
You probably have made the upgrade on your code, but the changes were not pushed to our servers.
So here is the process:
You do the changes in your code (ideally in a development environment, see this documentation if needed - be aware that pushing changes directly on remote environment is prohibited by default)
You restart your server
You should see the liana_version correctly updated in the forestadmin-schema.json file, and you should a message in your console logs informing that it was sent (something like: Schema was updated, sending new version).
I can see you’ve create a development environment, that’s the right way to go.
So now:
Upgrade your forest-express-sequelize version on your development environment
You should see the right version on your forestadmin-schema
You can also check that everything is working fine on the UI after this upgrade
Then you deploy your changes (I’m talking about file changes on your repo here) to your remote and production instances.
That should be it!
(Deeper explanation: to make the process safer, we are updating the forestadmin-schema and sending it to our servers on agent restart only when the environment is of type development. Because normally you test it first on development and then propagate the changes on remote environment if everything is alright. There exists bypasses but we don’t recommend them).