How does yarn interprets a dependency's semver that does not provide the patch version

Question

My question is about how yarn.lock handles updates between libraries.

I was wondering given a project A that uses a library B, that library uses a library C: A uses B