Changelog generation & testing #25
Conversation
| /** | ||
| * Compares two versions and returns the type of update that is required to go from oldVersion to newVersion. | ||
| * Takes into account that versions may be rolled back. For example: | ||
| * - 1.0.1 -> 1.0.0 is a patch update |
There was a problem hiding this comment.
Assuming that the library authors are very strictly following early semver. In my experience, not all libraries/maintainers follow this scheme: they will add small features in patches and only bump minors for more significant changes. Furthermore, as far as I know the tooling (i.e. MiMa) is not currently able to programmatically enforce strict early-semver, so this is relying on maintainers best efforts.
Maybe that's okay for toolkit, just pointing it out.
There was a problem hiding this comment.
I want to solve it with the list of exceptions. If it's impossible to follow that, then ok, but let's have a list showing where it breaks.
As for the changes, it's a tool to hold it all together, enforcing it on specific libraries is of course a separate problem that has to be addressed.
checks/Dependencies.scala
Outdated
| case _ => None | ||
|
|
||
|
|
||
| sealed abstract class VersionDiff(val order: Int) extends Ordered[VersionDiff]: |
There was a problem hiding this comment.
if this was a Java style enum then that would avoid all the boilerplate :(
There was a problem hiding this comment.
enum VersionDiff extends Enum[VersionDiff]:
case PatchUpdate, MinorUpdate, MajorUpdate
val order = ordinal
Program to traverse the dependency trees and check semver compliance, and generate changelogs.