support Unity 2018.1.x

[basisbit]

When trying to use the scripts of this repo for a Unity 2018.1.x based project, any unit tests and also any building on macOS seems to be impossible because of changed requirements regarding software activation:
https://forum.unity.com/threads/package-manager-failed-to-resolve-packages-packages-directory-does-not-exist.522782/
Basically, it either requires a Unity Pro serial number or previously an activation of the Unity setup in GUI, and then providing login credentials.
Any idea, if a workaround might be possible, by manually setting whatever file as "this system is already activated"?

[SebastianJay]

Hey there -- I've been away from this space, so I don't know a workaround. Based on that thread, it seems the new licensing requirements break this scenario for 2018.1. I'd recommend asking for this to be supported again at https://feedback.unity3d.com/ (I couldn't find a topic after some cursory searching; if you find or create one please link it here)

In the meantime, I can update the readme describing this limitation. Or, if anyone finds a workaround, we can discuss the code changes for that.