summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBundlerbot <bot@bundler.io>2019-04-23 18:55:25 +0000
committerBundlerbot <bot@bundler.io>2019-04-23 18:55:25 +0000
commit69bf2bf121dccb750d0d537ff9f7a57473b0120b (patch)
tree92c51ec689baa7343422f438ee978efabc1f7458
parent9d733d92abe4e492f07027fc5928a5a1172d6b31 (diff)
parent61885b10c8070248b1fe90eb378b89d379c127d8 (diff)
downloadbundler-69bf2bf121dccb750d0d537ff9f7a57473b0120b.tar.gz
Merge #7136
7136: Bump CI rubies to latest patch levels r=deivid-rodriguez a=deivid-rodriguez ### What was the end-user problem that led to this PR? The problem was that new rubies have been released, and we're not yet testing against them, ### What is your fix for the problem, implemented in this PR? My fix is to update our CI matrix. Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
-rw-r--r--.travis.yml8
1 files changed, 4 insertions, 4 deletions
diff --git a/.travis.yml b/.travis.yml
index 8581b190dc..65ca9bb54b 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -31,9 +31,9 @@ addons:
secure: "TrzIv116JLGUxm6PAUskCYrv8KTDguncKROVwbnjVPKTGDAgoDderd8JUdDEXrKoZ9qGLD2TPYKExt9/QDl71E+qHdWnVqWv4HKCUk2P9z/VLKzHuggOUBkCXiJUhjywUieCJhI3N92bfq2EjSBbu2/OFHqWOjLQ+QCooTEBjv8="
rvm:
- - 2.6.2
+ - 2.6.3
- 2.5.5
- - 2.4.5
+ - 2.4.6
stages:
- linting
@@ -51,7 +51,7 @@ env:
jobs:
include:
- - rvm: 2.6.2
+ - rvm: 2.6.3
script: rake rubocop
stage: linting
# Ruby 2.3 also tested in 2.x mode
@@ -66,7 +66,7 @@ jobs:
env: RGV=v2.7.9
stage: test
# Ruby 2.4, Rubygems 2.6
- - rvm: 2.4.5
+ - rvm: 2.4.6
env: RGV=v2.6.14
stage: test
# Ruby 2.3, Rubygems 2.5