force pypi release test to use new version number, hopefully dodge ca…

…ching issue where it installs old version instead. update README link to ruamel to new pypi url.

README.rst

@@ -1534,7 +1534,7 @@ pypyr has 100% test coverage. Shippable CI enforces this on all branches.
 Thank yous
 **********
 pypyr is fortunate to stand on the shoulders of a giant in the shape of the
-excellent `ruamel.yaml <https://pypi.python.org/pypi/ruamel.yaml>`_ library by
+excellent `ruamel.yaml <https://pypi.org/project/ruamel.yaml>`_ library by
 Anthon van der Neut for all yaml parsing and validation.
 
 **********

ops/shippable-pypi-release.sh

@@ -28,7 +28,7 @@ echo "----------Done with twine upload-------------------------------------"
 echo "----------Deploy to pypi complete. Testing in new virtual env.-------"
 
 # maybe need deactivate here, and then manually create new virtual env?
-pip install --upgrade --no-cache-dir pypyr
+pip install --upgrade --no-cache-dir pypyr==${NEW_VERSION}
 # pypyr --v will return "pypyr x.y.z" - get everything after the space for the
 # bare version number.
 TEST_DEPLOY_VERSION=`pypyr --v | cut -d " " -f2`