Best practices for versioning project after dependency upgrade
Posted
by
shabunc
on Programmers
See other posts from Programmers
or by shabunc
Published on 2012-10-12T12:11:37Z
Indexed on
2012/10/12
15:48 UTC
Read the original article
Hit count: 311
Say, my project have dependency N with version 1.0.0. Then something have changed, and I should depend on newer version - let it be 1.0.1.
OK, I'm incrementing dependency version, nothing else changes in my code. It looks like I should increment my own projects' version, but how exactly I should increment?
Should I increment only third number (so-called revision), or best practices here are more complicated. For example, may be, if we are changing projects' dependency minor value, we should do the same thing in the project itself?
© Programmers or respective owner
