1.6.0 breaks semver, should be 2.0.0

[ahill-mlft]

The backward compatibility issues in the changelog, especially the removal of public APIs, are pretty clear signals the major version should have been bumped. For example, the removal of the MessageStatic trait breaks the Prometheus crate currently on crates.io.

[stepancheg]

Probably you are right. Is there anything can be done now?

[ahill-mlft]

There is! You can yank version 1.6.0, then republish it as 2.0.0.

[stepancheg]

That will break crates which depend on 1.6, not sure it’s right thing now.

As a temporary solution I can suggest to explicitly depend on ~1.5 in your crates now.

Sorry again.

[bachp]

One solution would be to re-publish 1.5 as 1.7
And then re-release 1.6 as 2.0

[pamolloy]

@stepancheg @bachp's solution is a good one. Please follow that recommendation.

Like any bug when writing software, bumping a semver incorrectly happens, but it is important to fix it just like any other bug.

[stepancheg]

OK, republished version 1.7.1 from 1.5 branch. Not sure it's the best idea, but OK.

[stepancheg]

Republished 1.6 branch as 2.0.0.