You can register new versions of registered models by specifying the Git commit which corresponds to the new version.
You can register versions using the GTO command line interface (CLI). To register versions using Iterative Studio, watch this tutorial video or read on below:
On the models dashboard, open the 3-dot menu for the model whose version you
want to register. Then, click on
Register new version. The registration
action can also be initiated from the model details page or from the related
project’s experiment table - look for the
Register version button or icon.
Select the Git commit which corresponds to the new version of your model. If the desired commit does not appear in the commit picker, type in the 40-character sha-1 hash of the commit.
Enter a version name. Version names must start with the letter
v and should
follow the SemVer format after the letter
v. Below are some examples of
valid and invalid version names:
vin the beginning), v1.0 (missing the patch segment of the Semver, v1.0.new (using an invalid value
newas the patch number).
Optionally, provide a Git tag message.
Once the action is successful, the newly registered version will show up in
Latest version column of the models dashboard. Note that this will
happen only if the newly registered version is the greatest semantic version
for your model. For example, if your model already had v3.0.0 registered,
then if you register a smaller version (e.g., v2.0.0), then the new version
will not appear in the
Latest version column.
If you open the model details page, the newly registered version will be
available in the model
History section as well as in the versions drop
If you go to your Git repository, you will see that a new Git tag referencing the selected commit has been created, representing the new version.