3 ms·
As far as I can tell the latest Rails version (3.2.11) is not affected. Of course, I only noticed this after frantically updating my gems. Sigh.
by speleding 14y ago
As far as I can tell the latest Rails version (3.2.11) is not affected. Of course, I only noticed this after frantically updating my gems. Sigh.
- PetrolMan 14y agoDoesn't appear to affect 3.1.x or 3.2.x