How do users upgrade packages to the latest version using MPM?

I started creating an MPM repo for several different intertwined projects, but do not know how users are supposed to update the latest package version when I push a new change.

For example (which you can test) I can setup the repo and install WaveVortexModelDiagnostics version 1.0.1,

git clone https://github.com/JeffreyEarly/OceanKit.git
mpmAddRepository("OceanKit","path/to/folder/OceanKit.git")
mpminstall("WaveVortexModelDiagnostics@1.0.1");

which works great (lets assume most people installed it without specifying a version number, that was just the latest version at the time). So now they pull the new version of the repo want to upgrade packages to the latest version, but if they run

mpminstall("WaveVortexModelDiagnostics", AllowVersionReplacement=true);

then they are told version 1.0.1 is already installed. The only way around this that I can tell is to manually specify the current version number of each package,

mpminstall("WaveVortexModelDiagnostics@1.0.2", AllowVersionReplacement=true);

which is obviously very cumbersome and not straightforward.

Is there a recommended solution for this?

(FWIW there is a related thread on this topic which does not appear to be correctly resolved).