That was golang.org/x/crypto's fault for using internals not covered by the compatibility promise [0], sorry about that. However, we try to hold x/crypto itsel

That was golang.org/x/crypto's fault for using internals not covered by the compatibility promise [0], sorry about that. However, we try to hold x/crypto itself to the same compatibility standard as the standard library, so I think simply updating x/crypto at the same time should have made it a smooth update. [0]: https://news.ycombinator.com/item?id=23164795 https://news.ycombinator.com/item?id=23164795