It fixes possible problems for STI (discovery plugins): https://github.com/rails/rails/commit/257d65ed2ceb14dca6b1319355ed4f8a73540498 Here is the associated issue: https://github.com/rails/rails/issues/14785 As it was described in: https://bugzilla.redhat.com/show_bug.cgi?id=1357583 This is data integrity bug, high importance, z-stream candidate.
Rails is provided by RHSCL and bugs relating to updating the version in a particular SCL should be directed there I feel given they maintain the SCL and patch levels on top.
I don't think that update to Rails 4.1.6+ is feasible, but I think that applying the patch linked in comment #1 should be doable. Nevertheless, would you mind to elaborate what is the impact of the issues, to help us prioritize? From the bug 1357583, I'd say that you have workaround in place ...
Removing devel_ack set from previous team.
You are right, Vít. We have a workaround in 6.2. I thought you regularly upgrade but it looks like you only backport security issues. Therefore we can close it.