Hi Praveen,
I need to admit that I perfectly understand your wish. However, I think
this might go beyond the intended purpose of this small script which I
wrote to solve *routine* tasks. It is not really intended to do
everything absolutely automated - developer checks should be done in
normal
Package: routine-update
Version: 0.1.5
Severity: wishlist
I think targeting experimental for breaking changes is a safer default
than picking unstable by default.
As per semver.org, for libraries without a public API, ie, version <
1.0, even minor updates can be breaking - even if it does
2 matches
Mail list logo
