Resilient to rewriting history

[ecattez]

Rule

CBD must be resilient when the git history is squashed or forced to change.

• A new tag should be created if the git history has been squashed with additional changes from the last known commit.
  • The tag must always starts from the last known version
  • If no tag exist, new tag is 0.0.1
• No version should be created if the git history has been squashed only.

Background

Current tag: 0.2.0 (c5)

Commit hash	Short message
c1	init project
c2	feat: first feature
c3	refactor: some refacto
c4	fix: a bug to fix
c5	feat(some scope): second feature
c6	tech: some tech
c7	doc(readme): write some doc

Example 1: Rewriting history did not affect versioning

-- Squash from c1 to c6 --

Commit hash	Short message
cA	feat: epic one is done
c7	doc(readme): write some doc

Expected tag: 0.2.0 (c5)

Example 2: Squash to feat with additional changes

-- Squash from c1 to c6 --
+ some changes

Commit hash	Short message
cA	feat: epic one is done with some changes
c7	doc(readme): write some doc

Expected tag: 0.3.0 (cA)

Example 3: Squash to fix with additional changes

-- Squash from c1 to c6 --
+ some changes

Commit hash	Short message
cA	fix: epic one is done with some changes
c7	doc(readme): write some doc

Expected tag: 0.2.1 (cA)

Example 4: Squash to breaking changes with additional changes

-- Squash from c1 to c6 --
+ some changes

Commit hash	Short message
cA	epic!: epic one is done with some changes
c7	doc(readme): write some doc

Expected tag: 1.0.0 (cA)