Revision 6bec4170570e0dfabe6a3e724bc90f38dcaf7e2a authored by brharrington on 06 April 2018, 23:10:50 UTC, committed by GitHub on 06 April 2018, 23:10:50 UTC
This is mostly just to trigger a change to verify the
release. The previous attempt at 1.6.0-rc.10 failed
because it was still trying to publish 1.6.0-rc.9. The
theory is that this is because they were both tagging
the same commit.
1 parent 44e2f58
History

README.md

back to top