[jjnoakes]

Still don't see the big problem. If the major version is updated and it doesn't affect you, you have a 10 second job to do. If it does, you have a bigger job to do (or don't update).

What's the big deal?

[sheepmullet]

How do you know if it's a 10 second job or a bigger job?

[jjnoakes]

Read the release notes?

Read the code diff?

Try it?

[sheepmullet]

So lots of manual work. And you still don't see the issue?

Wouldn't it be good if there was some kind of automated way to know?

[klibertp]

But without semver you'd need to do this manual work even more often! Semver makes you do less manual labor, because you know that PATCH and MINOR don't require your attention. You don't know such a thing in many other versioning schemes.

Would it be better to eliminate even more manual labor? Yes, of course. But then is semver bad because it reduces manual labor?

[prayerslayer]

I get your overall point that it's better than nothing, but you'll have to admit semver makes promises that just don't hold up in reality:

> because you know that PATCH and MINOR don't require your attention

:)

In 99 % of cases, they don't. But you're never completely sure.

[jjnoakes]

Semver doesn't preclude automating anything, does it?