fix: update major version on preid

[Tristan-gu]

Is there an existing issue for this?

• I have searched the existing issues.

Version

6.2.0

Description

When you are working on preid version, if you commit a breaking change, the major version is not updating.

See discussion for details.

Steps to reproduce

1. create a preid version
2. push a breaking change commit
3. create a new preid version

Expected behavior

Honnestly, I read docs here SemVer, and I don't find exactly what we are supposed to do in this situation.

As far as I'm concerned, there's a lack of clarity on this subject, especially when it comes to pre-release versions.
I don't know whether you absolutely have to mount the major version or not in the case of a pre-release, because in that case, it's the same thing for the minor version and the patch.

If you mount the version in all cases, for the consumer of the pre-release library, it's going to be complicated to follow because if the version goes from 1.0.0.beta.0 to 1.1.2.beta.1 for example, you'll never be able to declare the dependency in the pubspec.yaml in this way

my_package: ^1.0.0.beta.0

But only in this way

my_package: '>=1.0.0 <2.0.0'

I'm not sure this is the best way to declare dependancies.

Screenshots

No response

Additional context and comments

No response