We saw the same issue in our builds. From what I can see, the version of ruby that is pointed to in the “$(travis_internal_ruby)” variable is locked to a version to support their build scripts. This looks to have caused an issue with the latest release of dpl requiring a higher ruby version.
Short term, we are using the following option in our .travis.yml file to “lock” the dpl version to the previous release until a fix is found. Just wanted to share in case it can help others as all of our deploys were erroring until adding the branch option. This may break later, but it works now for us.
I am providing the partial block out of context and we use the script provider, so please adjust to fit your needs. Prior, we just had “edge: true”.
deploy:
provider: script
edge:
branch: v2.0.3-beta.4