Cow currently tries to update all constraints, even some that arguably shouldn't be touch.
e.g. recipe-blog 1.x-dev has a requirement for recipe-cms: ^4. When recipe-blog gets tag, cow rewrites that to match the something like recipe-cms: ~4.10.0
I don't think the intention here was to lockstep recipe-blog to recipe-cms.
Acceptance criteria
[ ] Cow only updates a contstraint if it ends in .x-dev.
Cow currently tries to update all constraints, even some that arguably shouldn't be touch.
e.g.
recipe-blog1.x-dev has a requirement forrecipe-cms: ^4. Whenrecipe-bloggets tag, cow rewrites that to match the something likerecipe-cms: ~4.10.0I don't think the intention here was to lockstep recipe-blog to recipe-cms.
Acceptance criteria
.x-dev.