Travis fails on all PRs about containerregistry HOT 3 CLOSED

Does anyone at Google own this?

from containerregistry.

I will look into this.

from containerregistry.

By default, Travis tests fail on all external PRs due to security reason: https://docs.travis-ci.com/user/pull-requests/#pull-requests-and-security-restrictions
You are correct. We do use secret environment variables for logins. During Travis run, contributors can run malicious scripts to get those credentials and we of course don't want that.

There are ways to work around, e.g. https://blog.algolia.com/travis-encrypted-variables-external-contributions/ and discussion about it, e.g. OHDSI/Achilles#165

Since currently there's no plan to maintain this repository, I would only consider urgent CLs to merge in our codebase. Our suggestion is to migrate to our Golang library as Github is the source of truth for the repo and is actively maintained - https://github.com/google/go-containerregistry

Thanks for your understanding.

from containerregistry.