Indicating breaking changes in plugins with automated releases

Thanks for the update to the docs that clarifies this.

If a plugin has manual control of the major prefix, i.e. ${revision}.${changelist}, and the revision is bumped from 1 to 2, what does the generated changelist become in the first release of the 2.x line?

Does it go back to the start i.e. something like

1.122.vabcd...
1.123.vabcd...
2.0.vabcd...

Or does it continue counting the number of Git commits upwards e.g.

1.122.vabcd...
1.123.vabcd...
2.124.vabcd...