So I'm really iffy about this change.  It seems like a compensation for lower level code not catching the exceptions thrown by the transport classes.  Just on a quick overview, we throw a `UnexpectedValueException` if the response can't be parsed properly, and there's a couple of places where a `RuntimeException` is thrown.  All of these impact more than just a GET request.  I'd say let the update adapter catch exceptions from the transports instead of checking in it for a boolean false as you've proposed here.

And there's always Option C.  The HTTP package in the CMS is out of sync with that of the Platform, which includes a patch you provided to deal with this type of scenario (joomla/joomla-platform@3b8ad8265bb07cf5ce1c3e9fcf02cff2dfb7615e).