manager_version should match the tagged version
frosty-geek opened this issue · 2 comments
Looking at the initial setup docs for seed nodes there is no mention how to specify the OSISM Release we want to deploy.
the tagged version of the cookiecutter repo lists manager_version as "latest".
release.osism.tech tells you how to manually set the version you want to deploy instead of latest
When you run the cookiecutter, you will be asked for the version of the manager. If you enter 4.2.0 instead of latest, this will be used accordingly.
The tag on this repository with the 4.2.0 is a tag and not a branch. Therefore, the version there is also set by default to latest and not to 4.2.0.
The tag only means that this tagged status works together with the 4.2.0 release.
@frosty-geek Please have a look at #418.