I would agree if that error was being raised by anything that actually checked if a release was valid. Even internally, InvalidRelease suggests that the module exists but the requested version/release doesn't. That's not what this error represents. We can always add an InvalidRelease error if needed later on.