ThermalNetwork version has been updated. We grab the newest patch version when we install, because we use tilde-version here. However, this if statement wants the version to match exactly, including patch version, so we output the "incorrect version" message. In this case, that's an erroneous message, but perhaps not always? During heavy development, I can imagine that sometimes the patch level could contain breaking changes. Or should we change the logic for that incorrect version message?
Decided to install exact dependency versions to eliminate this problem. In the distant future when versions are more stable we can revisit this.
Checklist (Delete lines that don't apply)
[ ] Unit tests have been added or updated
[x] All ci tests pass (green)
[ ] An issue has been created (which will be used for the changelog)
Resolves #[issue number here]
Pull Request Description
ThermalNetwork version has been updated. We grab the newest patch version when we install, because we use tilde-version here. However, this if statement wants the version to match exactly, including patch version, so we output the "incorrect version" message. In this case, that's an erroneous message, but perhaps not always? During heavy development, I can imagine that sometimes the patch level could contain breaking changes. Or should we change the logic for that incorrect version message?
Decided to install exact dependency versions to eliminate this problem. In the distant future when versions are more stable we can revisit this.
Checklist (Delete lines that don't apply)