We have seen cases where a dev was having trouble getting stim to work and it ended up being a very old version of stim that had some breaking behavior associated with it. It would be nice if you could specify a minimum stim version somewhere in the stim.deploy.yaml that would immediately bail with an error that the version of stim you are using is less than required by the stim.deploy.yaml. (IMHO it's important to verbosely state that it's specified in the config file as opposed to some obscure, on-the-net check that stim is doing itself against some public "versions" server.)
In the "deployment" section is where this seems to be the best heirarchical placement, but it would require adding some kind of sub-section where you can set minimum and highest versions this config is expected to safely run:
We have seen cases where a dev was having trouble getting stim to work and it ended up being a very old version of stim that had some breaking behavior associated with it. It would be nice if you could specify a minimum stim version somewhere in the stim.deploy.yaml that would immediately bail with an error that the version of stim you are using is less than required by the stim.deploy.yaml. (IMHO it's important to verbosely state that it's specified in the config file as opposed to some obscure, on-the-net check that stim is doing itself against some public "versions" server.)
In the "deployment" section is where this seems to be the best heirarchical placement, but it would require adding some kind of sub-section where you can set minimum and highest versions this config is expected to safely run:
There may well be much better location for this than in the deployment section.
If no min/max is specified in the config, the checks should probably not be performed at all.