tree 57902eb105ef60e84cdce0ad1ac4d29ff6726b29
parent f1475299afd41815c78c3768253468ea622669f3
author aiuto <aiuto@google.com> 1570215359 -0400
committer GitHub <noreply@github.com> 1570215359 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJdl5W/CRBK7hj4Ov3rIwAAdHIIAFHQpccxZW0D/LWBJgEO2/tO
 URm4UO1iPCQD96d+fVsG9qdxQbPskHqaPDuYUfiq3S4RzBhv7At6pIAJTYMMw0MF
 u2MxbDK5eB39X63GbJ1UxJkWOyMttyq0jFQZ7JgiZWPB4FlzVeyW8K+e5XrysXkv
 P7velWZf5EJ59mP/HaNMUkBnZKoVxpCNNGJKNrNs5uXNTHLEVrPxABf3JLOvW0FC
 SSrhZpI5b66I2Qy/HBPZnPJAuWKn6kPn/tswyiVP2lpZQue/IiFGUs/GS17YnUd3
 bpcx7w6YTw1MU+Y0sW54rEz203hkHgj0/TYr7hDIB0u5VL8+529ZhRstjayZXhM=
 =oiF0
 -----END PGP SIGNATURE-----
 

Update version and changelog in prep for 1.0.0 release (#196)

* -Update changelog to get ready for release 1.0
-Change README to point to releases page for WORKSPACE setup. Otherwise
 the readme shipped in the archive can never be in sync with the readme
 that has the correct sha256.

* update incompatible changes

* -Update changelog to get ready for release 1.0
-Change README to point to releases page for WORKSPACE setup. Otherwise
 the readme shipped in the archive can never be in sync with the readme
 that has the correct sha256.

* fix wording of changelog

* remove false file