Override version

[bvssvni]

Currently it is not possible to simulate breaking changes because override-version property in the extract format is ignored.

[bvssvni]

The original idea was that simulation a breaking change is done by replacing an extracted version with a newer version. The newer version causes updates where there otherwise would be none. This answers questions such as "assume we introduce a breaking change here, what consequences will it have?".

[bvssvni]

The problem is that when overriding with an older version, it can lead to several classes of errors:

• The algorithm that generates update information assumes that the packages always have the latest version (greater or equal than used in any dependency). Overriding with an older version might lead to unsound actions.
• It is easy to forget that you have inserted override information. For example, you increment a version, run the analysis, then the package increments for real, everything seems fine, then it increments again for real, and suddenly the update information contain unsound actions.

It seems that adding this feature will introduce more problems than it solves.

[bvssvni]

Due to the problems above, won't add this feature.