You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you create an annotated version tag with a message like so:
git tag -m "Message" 0.2.0
The tag will not be considered when calculating the next tag.
So given the following commits where 0.2.0 is annotated, the calculated next version will be 0.2.0 because 0.2.0 is ignored and 0.1.0 is used as a starting point.
9f807d5 feat: Feature D
9f807d4 feat: Feature C (tag: 0.2.0)
9f807d3 feat: Feature B (tag: 0.1.0)
9f807d2 feat: Feature A
9f807d1 chore: Inital commit (tag: 0.0.1)
The next tag in this example should be 0.3.0.
The text was updated successfully, but these errors were encountered:
If you create an annotated version tag with a message like so:
git tag -m "Message" 0.2.0
The tag will not be considered when calculating the next tag.
So given the following commits where
0.2.0
is annotated, the calculated next version will be0.2.0
because0.2.0
is ignored and0.1.0
is used as a starting point.9f807d5 feat: Feature D
9f807d4 feat: Feature C (tag: 0.2.0)
9f807d3 feat: Feature B (tag: 0.1.0)
9f807d2 feat: Feature A
9f807d1 chore: Inital commit (tag: 0.0.1)
The next tag in this example should be
0.3.0
.The text was updated successfully, but these errors were encountered: