You can remove the outdated check in the protected branch settings of the repository settings.
Hm, it seems that stacktraces are somehow broken (maybe due to OTP 23?). With verbose:
Failed: The input fails the test. An exception was raised: ** (FunctionClauseError) no function clause matching in DateTime.to_unix/2 Stacktrace:
The actual stacktrace is not being written. PropCheck as of v1.3.0.
PROPCHECK_DETECT_EXCEPTIONS=1; with that, the exception is output in red.
I guess that pointing to a dedicated git-sha is not a very good option. What do you think?
You mean pointing to a git revision within the published version of PropCheck? I don't know if this is something that is frowned upon.. How about this: We point to PropEr's git revision, but only release a RC candidate. With that, the update of PropCheck should not automatically propagate to users, unless they explicitly switch to the RC version.