(1.0.0), twitter (1.0.0) → jsonLib (1.0.0) • facebook (1.1.0) comes out → jsonLib (1.1.0) •Can’t update! twitter locked to jsonLib (1.0.0) • Common when dep. mgnt relies on `exact` versions such as strong naming, e.g. • COM scenarios (Office Addins)
• Can safely update without fear •It’s simple {major}.{minor}.{patch}-{tag}+{buildmetadata} • major = breaking change • minor = feature • patch = bugfix
-> 1.0.1-feature-foo.1+1 (PR #5 Version: `1.0.1-PullRequest.5+2`) 7c2438 -> 1.0.1-feature-foo.1+2 (PR #5 Version: `1.0.1-PullRequest.5+3`) 5f413b -> 1.0.1+4 d6155b -> 2.0.0-rc.1+0 (Before and after tag) d53ab6 -> 2.0.0-rc.2+1 (Pre-release number was bumped because of the tag on previous commit) b5d142 -> 2.0.0+0 (2.0.0 branch was merged, so master is now at 2.0.0) http://gitversion.readthedocs.org/en/latest/examples/