Let's align integration versioning semantic to the real world things.
Currently versioning uses 3 digits semantics x.y.z (e. g. 1.6.2). I propose to keep it as is, but repurpose numbers meaning.
x - major version let align it with serenity-core version to make compatibility more transparent. E. g. version 2.x.x is compatible with Serenity 2.x, version 3.x.x is compatible with Serenity 3.x and so on.
y - minor version for updating report portal dependencies. E. g. change from 2.1.x to 2.2.x means RP dependency version was incremented both major or minor versions.
z - path version for new integration feature and bugfixes.
Let's align integration versioning semantic to the real world things. Currently versioning uses 3 digits semantics x.y.z (e. g. 1.6.2). I propose to keep it as is, but repurpose numbers meaning. x - major version let align it with serenity-core version to make compatibility more transparent. E. g. version 2.x.x is compatible with Serenity 2.x, version 3.x.x is compatible with Serenity 3.x and so on. y - minor version for updating report portal dependencies. E. g. change from 2.1.x to 2.2.x means RP dependency version was incremented both major or minor versions. z - path version for new integration feature and bugfixes.