An in-range update of selenium-server is breaking the build 🚨

[greenkeeper]

Version 3.5.0 of selenium-server just got published.

Branch	Build failing 🚨
Dependency	selenium-server
Current Version	3.4.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As selenium-server is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 2 commits.

• 4752522 updated to 3.5.0
• 7d82246 use package version to generate the name of the jar file

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 3.4.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

Version 3.5.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

[greenkeeper]

Version 3.5.2 just got published.

Your tests are still failing with this version. Compare the changes 🚨

[greenkeeper]

Version 3.5.3 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 1 commits.

• 3c5b880 updated to 3.5.3

See the full diff

[greenkeeper]

Version 3.6.0 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 2 commits.

• 2de12e9 updated to 3.6.0
• 3c5b880 updated to 3.5.3

See the full diff

[greenkeeper]

Version 3.7.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 3 commits.

• f102654 updated to 3.7.0
• 2de12e9 updated to 3.6.0
• 3c5b880 updated to 3.5.3

See the full diff

[greenkeeper]

Version 3.7.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 1 commits.

• 4fc9256 updated to 3.7.1

See the full diff

[greenkeeper]

Version 3.8.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 1 commits.

• 40d7a14 updated to 3.8.0

See the full diff

[greenkeeper]

Version 3.8.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 1 commits.

• 0ac39b0 updated to 3.8.1

See the full diff

[greenkeeper]

Version 3.9.0 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 1 commits.

• 210cbb6 updated to 3.9.0

See the full diff

[greenkeeper]

Version 3.9.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 2 commits.

• 0cde2e2 updated to 3.9.1
• 210cbb6 updated to 3.9.0

See the full diff

[greenkeeper]

Version 3.10.0 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 2 commits.

• 0cde2e2 updated to 3.9.1
• 210cbb6 updated to 3.9.0

See the full diff

[greenkeeper]

Version 3.11.0 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 3 commits.

• 6b1bede updated to 3.10.0
• 0cde2e2 updated to 3.9.1
• 210cbb6 updated to 3.9.0

See the full diff