Pessimize generates overly restrictive requirements
Correct specification for semantic versioning is described in the RubyGems guides patterns for declaring dependencies. You lock users to a bug fix series and don't allow backward-compatible releases with new features.
For >= 1.2.3 the semantic-versioning-safe requirement is ~> 1.2, >= 1.2.3.
I've added an example to the rubygems guides rubygems/guides@ef777b4c
Thanks for this, I completely agree.
I originally locked it to patch level upgrades because I had a project where a supposedly minor upgrade was not in fact backwards compatible. But it shouldn't be the default any more.
I'm planning on adding options to the command line script, which will give the user the choice of how restrictive/permissive they are with their version upgrades.
Thanks again
I'm finally going to tackle this one for the next version release. I'll post updates here.
Thanks