Dependencies deprecation and how to identify it

It seems to me (check Tracker #4656: Drop Ruby 1.8 support - Foreman) that we
are often hitting many dependencies break our test_develop job in Jenkins
after 1.8 is deprecated or the API changes or some bug breaks it (I'm
writing this mail because now test_develop is broken for 1.8 because of a
bug on apipie-rails for 0.2.3 -

We usually notice it ourselves after seeing that PR tests are broken. It's
not terrible and generally we fix the issue in a day.
Anyway I wonder if there is some tool or something we could start to use to
notify this automatically when it's clear that a dependency is failing, or
if adding this to Jenkins is just not worth the trouble.

ยทยทยท -- Daniel Lobato