updating a dependency could affect the API about semver.org HOT 4 CLOSED

In this case, if you don't want to update your API, you'll have to wrap the the lower level API and ensure the results your API returns stay the same. Wrapping other lower level API's always means you should try to isolate your users from changes in those lowerlevel API's.

from semver.org.

I agree with @beoran. The public API is your responsibility as a library maintainer. If you upgrade a dependency, you need to make sure your API is not affected. Automated test suites are great for this kind of verification.

from semver.org.

I agree, my point was that the FAQ makes the assumption that a dependency can't affect your API. I felt that this isn't true in all cases and it seems we are in agreement.

from semver.org.

Well, nice to see we're all agreeing. :)
I think it's best the FAQ should be corrected to state something like what mojombo said.

from semver.org.