Updating a few gems #1101

Closed
wants to merge 6 commits into
from

Projects

None yet

4 participants

@cesy
Member
cesy commented Dec 1, 2016

Let's have some December updates

@cesy cesy Updating a few gems
d572f33
@maco maco added the in progress label Dec 1, 2016
@cesy
Member
cesy commented Dec 1, 2016

Looks like we need to make some changes for CodeClimate and SimpleCov. Anyone want to have a go? Otherwise I'll look into it later.

@CloCkWeRX CloCkWeRX Merge branch 'dev' into gemupdate
a21eb71
@@ -147,17 +149,17 @@ GEM
json
thread
thread_safe
- elasticsearch (2.0.0)
@CloCkWeRX
CloCkWeRX Dec 1, 2016 edited Contributor

This one we want to avoid, the gem doesn't use semver. Right now its at elasticsearch 2.0.0; indicating API compatibility with elasticsearch 2.0.0. Upgrading to 5 warrants a corresponding elasticsearch upgrade.

It probably won't break anything too badly in terms of BC, but there are some things to watch out for (or at least that was my experience from 1.4 -> 2.0, a BC break every other release)

@@ -421,41 +423,37 @@ GEM
sprockets (>= 2.8, < 4.0)
sprockets-rails (>= 2.0, < 4.0)
tilt (>= 1.1, < 3)
- selenium-webdriver (2.53.4)
+ selenium-webdriver (3.0.3)
@CloCkWeRX
CloCkWeRX Dec 1, 2016 Contributor

Lets be narrower with webdriver, capybara, etc updates vs flakey CI (upgrade in individual commits so we can pinpoint regressions)

Br3nda and others added some commits Dec 2, 2016
@Br3nda Br3nda Merge branch 'dev' into gemupdate
4f77ce6
@Br3nda Br3nda Merge branch 'dev' into gemupdate
5b20a65
@Br3nda Br3nda Merge branch 'dev' into gemupdate
70d009b
@CloCkWeRX CloCkWeRX Merge branch 'dev' into gemupdate
9d00269
@CloCkWeRX
Contributor

I might do another version of this one today, pinning us to the right elasticsearch etc - mind if I close?

@CloCkWeRX CloCkWeRX referenced this pull request Dec 9, 2016
Merged

2016 12 gem upgrades #1126

@CloCkWeRX
Contributor

Opened #1126

@CloCkWeRX CloCkWeRX closed this Dec 9, 2016
@CloCkWeRX CloCkWeRX removed the in progress label Dec 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment