Device definitions available as patch releases (#19)

[iwr-redmond]

• Switches automatic version bump from minor to patch
• Updated Readme file with compatible release operator sample

Resolves: #19

[cmdr2]

Thanks. I've given this a bit more thought, and how about this - I'll update the major version if there are breaking changes, and the minor version if there are simple code changes, and the patch version for device database changes.

So people can depend on the minor version if they want updated code changes (non-breaking) along with device updates. If they rely on the patch version, then they'll get device DB updates until the next set of non-breaking code changes.

Otherwise this will force me to make every non-breaking code change (or internal refactor) a patch update, which is semantically wrong. And the major version will be quite pointless then, since it'll never increment.

Curious to know your thoughts. Thanks

[iwr-redmond]

Sounds fine. I'll update the Readme text.

[iwr-redmond]

Just to confirm, running pip install 'torchruntime~=1.18' will install version 1.20.0.

[cmdr2]

Hi @iwr-redmond I've replied in the original issue, and pushed the changes for this (and updated the readme).

https://github.com/easydiffusion/torchruntime#versioning-scheme

Just to confirm, running pip install 'torchruntime~=1.18' will install version 1.20.0.

Maybe my understanding is incorrect, but wouldn't that only result in 1.18.0, 1.18.1 etc, but not 1.20.0? To get any minor version, wouldn't you have to target torchruntime ~= 1?

Closing this PR since the original purpose has been resolved.

[cmdr2]

Thanks a lot for bringing this up, and for your help! :)