|
|
|
|
|
|
by prof_hobart
3448 days ago
|
|
|
Maybe I'm missing something, but to me more frequent builds make proper semver more important, not less. An easy way of knowing which versions you should be able safely update to without breaking changes seems hugely valuable. He talks about APIs versioning, but APIs are only a small part of the problem. How about the hundreds of libraries that my site is built with for example? Semver allows me to specify rules in my package file about whether to take only the exact version that I want, the latest patch, or the latest minor version. I didn't spot anything in the article that showed a better way of doing that. |
|
|