since different cli versions can represent big behavior changes (and the cli reflects the current version of what is running in the cloud project i think) we need to make sure everyone working on a project has the same cli version when they're working locally. e.g. today one of my engineers had an issue because he hadn't yet updated the nhost cli and it contained a big storage.files permissions behavior change. is there any way to "pin" the version somehow or how do others handle this?

@sheena No, but we're actively working on a new Nhost configuration file (nhost/config.*) where you will eventually be able to set the version for each service (Hasura, Auth, Storage) which will help with problems missmatching environment between engineers and local vs cloud settings.

nice, thanks