Having to bump wally.toml version every update can lead to scenarios where you need to make an additional commit after publishing, solely to use the wally publish command. Mistakes can also be made, as basically any version string is allowed- for example, I believe the version "0.4.00" is valid.
Considering wally publish is a permanent command, I think it makes sense to add a wally publish --bump(major minor or patch) feature. Alongside being nice QoL, it also ensures semver compliance, which is a good thing.
Having to bump
wally.tomlversion every update can lead to scenarios where you need to make an additional commit after publishing, solely to use thewally publishcommand. Mistakes can also be made, as basically any version string is allowed- for example, I believe the version "0.4.00" is valid.Considering
wally publishis a permanent command, I think it makes sense to add awally publish --bump(major minor or patch)feature. Alongside being nice QoL, it also ensures semver compliance, which is a good thing.