Travis failing to publish tag to pypi about pystac HOT 2 CLOSED

Pretty confused about this - I got an email saying v0.3.4 passed, and there's now a 0.3.4 package on pypi. But when I look at travis build history I still see the v0.3.4 branch as failing:

This is the successful build I was emailed about, which I don't see in travis history: https://travis-ci.org/github/azavea/pystac/builds/700450517

Perhaps an outcome of this issue will be to move off of Travis CI for build and publish, and onto GitHub Actions, which might have a more clear audit trail for builds and decreasing complexity by removing a 3rd party service.

from pystac.

I think that Travis is active on both travis-ci.org and travis-ci.com. It looks like the tagged commit for .org succeeded, but the one for .com failed. My suspicion is that the credentials were encrypted to target .org and not .com.

I attempted to disable builds in the .com platform (even though .org is seen as the legacy version) to reduce confusion. I agree on the true path forward being GitHub Actions, but think that a pystac migration would benefit from the CI transition work we plan to execute on next sprint in azavea/django-ecsmanage#20.

from pystac.